How to know if client loses connection, etc
Last question :)
Is there a way to know from the web service end to tell if a user that has posted to the webservice has disconnected? Here's my scenario:
User posts to web service, some sql server inserts are completed, results from inserts are returned as a dataset, dataset is returned to the user.
What happens is if a user posts to the web service and disconnects, reboots, etc, the web service keeps running and completes successfully. From my client end I need the results that it would have returned, so it's causing problems.
I figured I would check to see if there was an easy way to determine if the end-user was still 'there' and then commit the changes to the database accordingly.
Thanks for any help!
Tyler
I doubt there is any truly easy way to accomplish what you ask.
A good solution that I have implemented in the past for this, is to use the web service to create and submit a "job".
Then give the users a web page where they can go that shows the status of their job. You'll have to track result files on a peruser basis, and probably implement some kind of logon feature to prevent user a from seeing user b's results, but this method insures that an end user gets their results even if they have Client side issues. Now you won't even care if they are still "there" or not. And when they return, their results are ready.
Making the user re-run a process, especially since it sounds like what you are doing takes a lot of time, is usually REALLY annoying to the user, and in your situation will waste a lot of server resources and cause db problems.