[DUG] ISAPI Web service

[Matt Comb]

Rohit, this depends on your version of IIS.

IIS6 has this webservice extension caching mechansism that will create a new thread and a new instance of the webservice extension when load is high e.g. if two connections come in and access a webservice extension, and the second connection is kept waiting longer than a certain length of time (not sure what), it will create a new thread with a new instance of your webservice extension and serve the second connection off that.

Could you explain a little more what you are doing with your datasource within the dll? That migth help to explain what the issue is.

Regards,

Matt.





-----Original Message-----
From: "Rohit Gupta" <rohit at cfl.co.nz> 
Sent: Tue, 20 Sep 2005 13:33:11 +1200 
To: NZ Borland Developers Group - Delphi List <delphi at ns3.123.co.nz>
Subject: [DUG] ISAPI Web service 


I am confused.  I understood that a webservice dll was instantiated 
for each webservice function invokation.  certainly the dotnet 
webservice works this way.

Why doesnt the ISAPI ?  I have just inherited one and the 
datamodule in it is created only once.  The problem with it is that it 
is written with the assumption that each invocation was instantiating 
a new dll.  Mutiple concurrent users crash it.  :-(
Regards

Rohit

====================================================
==================
CFL - Computer Fanatics Ltd.  21 Barry's Point Road, AKL, New 
Zealand
PH    (649) 489-2280 
FX    (649) 489-2290
email rohit at cfl.co.nz  or  r.gupta at xtra.co.nz
====================================================
==================


_______________________________________________
Delphi mailing list
Delphi at ns3.123.co.nz
http://ns3.123.co.nz/mailman/listinfo/delphi