Re: Single instance???
- From: Rafal Gwizdala <gwrafal@xxxxxxxxxxxxxx>
- Date: Mon, 11 Apr 2005 22:57:01 +0200
erymuzuan wrote:
One way is you can utilise ASP.Net Session state framework to achieve this. or you can create a singleton remoting object on the server.
regards erymuzuan mustapa
Sniper wrote:
Hi guys
I have facing a small problem, it's like this.
There is a web service which has a web method call OpenPublicConnection which will open a connection to the SQL Server, and there is a web method call StartTransaction to start a tranaction for the class level connection which is opened by the OpenPublicConection Method. But when I call StartTransaction it's retruing an error saing the connection is closed... ? Is there anyway to fix this?? is there anyway to keep the conneciton object alive in the server side till client call the StartTransaction Method after calling the OpenPublicConnection method...?
Thanks for your help
-Aruna
You could try to solve this problem, but I think the problem is in your web service design. You should not leave open database connections/transactions between web service calls - this is very inefficient and can cause many problems when clients will be making concurrent calls to your web service.
Better think how to make your web service stateless.
Best regards Rafal Gwizdala .
- References:
- Single instance???
- From: Sniper
- Re: Single instance???
- From: erymuzuan
- Single instance???
- Prev by Date: Re: IIS / Web Services Security threats
- Next by Date: SOAP Call Retrieval
- Previous by thread: Re: Single instance???
- Next by thread: Interacting with an Access database using a Web Service
- Index(es):
Relevant Pages
|