Re: Calling web services from .NET
- From: "Ramya A" <ramyaashok12@xxxxxxxxx>
- Date: 26 Jul 2006 14:47:26 -0700
I think this can be possible by utilizing a timer in your ASP page for
a set interval.
Eveytime the interval laspses, it comes back to the timer and calls the
webservice again if the response results are not yet received.
You can also use waitforresponse property on the HTTP request object
and check for readystate of the HTTP request object in addition to the
timer.
Hope this helps.
Ramya
Scott Baierl wrote:
I have an ASP.NET application that calls web services on another host. Is
there a way that you can control the lifetime of the underlying TCP
connections that .NET uses to make the web service calls? From what I
understand, by default, .NET is configured to use a maximum of two
connections, and those connections stay open for up to 100 seconds after the
last data was sent/received. Is there a way to control the lifetime of
those underlying connections? In other words, can I have .NET use a
different connection for each request, or, time out the existing connection
quickly, so that it needs to create a new connection more often than the 100
second default timeout? Thanks in advance.
.
- References:
- Calling web services from .NET
- From: Scott Baierl
- Calling web services from .NET
- Prev by Date: Switching between two web servers?
- Next by Date: Returning Table in webservice and updating using delta.
- Previous by thread: Re: Calling web services from .NET
- Next by thread: Re: Calling web services from .NET
- Index(es):
Relevant Pages
|