Re: Where to store the handle of a web service between requests?
- From: "Bruce Barker" <brubar_nospamplease_@xxxxxxxxxx>
- Date: Tue, 22 Nov 2005 10:03:24 -0800
store in the Application object and use a pool approach. you could add a
background thread to age the pool (close and delete aged connections).
note: most http based webservices are single shot and close the connection
automatically after every request. even if keepalive is set, its for only a
short period.
-- bruce (sqlwork.com)
"Max" <eurodude2011@xxxxxxxxx> wrote in message
news:1kbjpx4te1s3q.89g2dvulzyxp.dlg@xxxxxxxxxxxxx
> Hi,
>
> I am helping to build a web app that's pretty much a wrapper around a web
> service. The question now is how to store the handle of the web service
> object between requests. My client is using SQL server for session state
> so
> I don't think I can store the web service handle there since it's not
> serializable.
>
> Opening up a connection to this particular service is quite slow so I
> don't
> want to reopen it for every request.
>
> I am looking for suggestions how to store the web service handle. Any
> ideas?
>
> Thanks
>
> Hans
.
- Follow-Ups:
- References:
- Prev by Date: Why does Visual Studios randomly change code?!
- Next by Date: Re: Anyone here use FCKEditor for ASP.NET?
- Previous by thread: Where to store the handle of a web service between requests?
- Next by thread: Re: Where to store the handle of a web service between requests?
- Index(es):
Relevant Pages
|