470,855 Members | 1,140 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,855 developers. It's quick & easy.

What happens on server following asynchronous client .Abort()?

I have questions regarding what happens on the web server side during an
asynchronous web method call when the client aborts its request via .Abort()

Background: My client app asynchronously calls a web method in a "broker"
web service that I've written. My broker service method in turn
synchronously calls another web service to perform backend processing. This
second, synchronous call can take up to a minute to return. My client-side
UI implements a Cancel button that results in a client-side .Abort() call if
the user clicks Cancel.

Does anyone know the details of what happens in my broker service following
the client .Abort() and how that effects the broker service's synchronous
call to the backend service? Will that request continue? Will it be
aborted? Is there a way I can detect or trap on the server-side that the
client aborted its call? Do I risk resource leaks or performance degradation
on my server or the backend server over time as users Cancel their requests?

Any insight or referrals to other info on this topic is much appreciated!
Aug 11 '06 #1
0 1110

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

7 posts views Thread by Colin | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.