Hi Peter,
Regarding on the scenario you mentioned, when the web application consumer
close the webbrowser, the ASP.NET server-side will not get any rapid
notification of it. It does be a very common and typical limitation of
http/web based application which is stateless with server.
If the reporting generation task is long-run and you feel it critical and
important to pause/cancel report generation whenever the client user close
the webbrowser(before the report generation finishes), I think you can can
consider the following approach:
** At your ASP.NET web application's page (which will let user send
request
for generating report), you need to add some additional code logic to to
contantly ping the webservice or windows service to as to let the backend
processing service know that the request client is still alive.
** you also need to apply a timeout policy at the report processing side.
e.g. if the genreation hasn't finsihed, but it hasn't received notify from
client side(to a certain sessionID) for a long time(exceed timeout), it
will cancel the generation.
for implementation, at web page side, you can consider using AJAX script
call to send notify to server-side constantly.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.