Re: Serious problem in using COM in IIS
From: J French (erewhon_at_nowhere.com)
Date: 07/28/04
- Next message: J French: "Re: Determine whether a cd-rw does an i/o operation"
- Previous message: Robert: "Re: Increasing GDI Object Limits"
- In reply to: Norton: "Serious problem in using COM in IIS"
- Next in thread: Tony Proctor: "Re: Serious problem in using COM in IIS"
- Reply: Tony Proctor: "Re: Serious problem in using COM in IIS"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 28 Jul 2004 12:33:23 +0000 (UTC)
On Fri, 23 Jul 2004 09:51:33 +0800, "Norton" <nortonwong@hotmail.com>
wrote:
>Hi all
>
>I have problem in using a COM object in IIS
>a COM named "ABC" was used in some ASP pages and i create an instance for
>ABC by using the following code
>
>Dim oObject
>Set oObject= Server.CreateObject("TestCOM")
>With oObject
> .Init '<--a custom command to clear all variable
> .Country= Application("CountryCode")
> .Criteria = Request("Criteria")
> .Process
> .Destory '<--a custom command to clear all variable
>End With
>Set oObject = Nothing
>
>When i use the object over time, the object instance will share some public
>variables defined in my ABC COM
Is this thing 'Single Use' or 'Multi Use'
It looks like 'Multi Use' to me
Any DoEvents would then allow something else in to corrupt your
variables
Not a problem, just create 'Handles' for each user and have an array
of UDTs referred to by each 'handle'
- Next message: J French: "Re: Determine whether a cd-rw does an i/o operation"
- Previous message: Robert: "Re: Increasing GDI Object Limits"
- In reply to: Norton: "Serious problem in using COM in IIS"
- Next in thread: Tony Proctor: "Re: Serious problem in using COM in IIS"
- Reply: Tony Proctor: "Re: Serious problem in using COM in IIS"
- Messages sorted by: [ date ] [ thread ]