M
mr boombastic
I'm asking this coming from Delphi devlopment for web services.
My asp.net web sercvice need to connect to a codebase database. To do
this it has to initialize and open a connection to the databse and read
tables which is time consuming. With Delphi I can get the webmodules to
do this during the initialization then and they stay open - when the web
service methods get called -they refer to the connections/tables opened
by that web module (i.e. the same thread). This is like pooled
conections..
My wuatyion then is can ASP dot Net do something similar - ie. can I
maintain a cache of open databse connections for codebase that I can use
or am I stuck with reopening the connection for each method call.
ideally I would like an initialization event for a webservice instance -
to open the connection used by any web method for that instance and to
keep the connection available during the lifetime of all the methods.
Is it possible to do likewise with asp.net web services?
My asp.net web sercvice need to connect to a codebase database. To do
this it has to initialize and open a connection to the databse and read
tables which is time consuming. With Delphi I can get the webmodules to
do this during the initialization then and they stay open - when the web
service methods get called -they refer to the connections/tables opened
by that web module (i.e. the same thread). This is like pooled
conections..
My wuatyion then is can ASP dot Net do something similar - ie. can I
maintain a cache of open databse connections for codebase that I can use
or am I stuck with reopening the connection for each method call.
ideally I would like an initialization event for a webservice instance -
to open the connection used by any web method for that instance and to
keep the connection available during the lifetime of all the methods.
Is it possible to do likewise with asp.net web services?