|
-
Jun 23rd, 2001, 10:14 AM
#1
Thread Starter
Hyperactive Member
Server.CreateObject and PWS vs IIS
Hi,
I have an ASP page that creates an Automation object for communicating to our main computer. When the page is run on PWS, a seperate instance of the object is created for each user which is what I want.
But when running under IIS, a single instance of the object is created in the system context and all users share this one object. When one user is accessing this object, all other users have to wait.
Questions:
Why? What does PWS do that IIS doesn't?
I've tried setting the isolated process in IIS and using Session objects to no avail.
Thanks,
Al.
A computer is a tool, not a toy.
-
Jun 23rd, 2001, 02:43 PM
#2
Frenzied Member
How is the component's instancing property set?
oOOo--oOOo
__ /\/\onte96
oOOo--oOOo
Senior Programmer/Analyst
MCP
[email protected]
[email protected]
Your results may vary.. some restrictions may apply.. pricing and participation may vary.. not available in all states.. professional driver closed course..quantities limited..
-
Jun 23rd, 2001, 05:29 PM
#3
Thread Starter
Hyperactive Member
I believe it is a single instance object because through VB only one instance is created when I try to create multiple instances. But it seems like through PWS, each user gets their own single instance of this object.
I'm wondering if MTS might be an answer but I know very little about this.
Thanks for the response.
Al.
A computer is a tool, not a toy.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|