User-434868552 posted
@
yhemanth
FWIW: (iis 5, not 6 ... do not know if it's a 6 problem too)
http://www.guidanceshare.com/wiki/ASP.NET_2.0_Performance_Guidelines_-_Design_Considerations
- HttpResponse.IsClientConnected. Consider using the HttpResponse.IsClientConnected property
to verify if the client is still connected before processing a request and performing expensive server-side operations.
However, this call may need to go out of process on IIS 5.0 and can be very expensive.
If you use it, measure whether it actually benefits your scenario.
also, imho, if the request is not likely to be expensive, it may be better to complete the request ... of course, for that, you need some way to separate inexpensive requests from expensive ones. while you can shorten the connect time timeout, i'm
not sure whether there is any way to specify how much time to allow beyond the connection ... alternatively, you could limit the number of rows returned.
g.
