Does ASP.NET continue reliably processing a request even after a user is navigated away via javascript?

Question

Environment:

• Windows Server 2003 - IIS 6.x
• ASP.NET 3.5 (C#)
• IE 7,8,9
• FF (whatever the latest 10 versions are)

Answer 1

How about don't do the async operation on an ASP.NET thread at all? Let the ASP.NET code call a service to queue the data search, then return to the browser with a token from the service, where it will then redirect to the result page that awaits the completed result? The result page will poll using the token from the service.

That way, you won't have to worry about whether or not ASP.NET will somehow learn that the browser has moved to a different page.