In this case, the request will run to completion and data will be returned to the web server, which will then throw it away (probably after realizing that the client's browser no longer wants it). Since Witango is not aware of the activities of the web browser (and really, the web server) it will continue on its way until it completes or hits an error.
There is no way to externally cancel a running request within Witango. The only possible recourse you would have is to periodically send data from the waiting client browser, say every ten seconds via javascript/ajax to your server. That "keep alive" would update a timestamp in memory. You could then monitor that timestamp throughout your application and cease processing if the stamp gets too old (therefore no longer being updated, therefore the user is not waiting for your results). You would normally do something like this in conjunction with thermometer or other "processing ." notice on the user's screen. Also, you might be asking about the interaction between Witango and your SQL server. This is the same issue, once sent a request, the SQL server will fully process that request even if the Witango server technically no longer needs it. There are a few ways that you can manage this, such as closing the ODBC connection or setting an execution threshold in the SQL server, however there is nothing that I know of that you can do programmatically to stop execution. If you are having an issue with something like this, I would make these suggestions: Limit the search criteria in such a way as to lessen the complexity of the searches. Optimize your database indexes, data types, etc. to improve performance. Install more compute cycles where necessary to provide necessary overhead. Robert _____ From: Ted Wolfley [mailto:[EMAIL PROTECTED] Sent: Friday, March 28, 2008 11:29 AM To: [email protected] Subject: Witango-Talk: cancel a query Hi, I have a site where a user can submit a complex query to search a 3.5+ million record table. Once submitted, the query is set-up to bring back only the first 1000 records. While waiting for the results, the user hits the back button or closes the browser window, how does Witango handle the cancelling of the query? Does the query still continue until the results are ready to be transferred to Witango? Is there a correct way to cancel the query and restore resources to the server? Ted Wolfley Lead Internet and Database Programmer The Ogden Group of Rochester phone: (585) 321 1060 x23 fax: (585) 321 0043 <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] <http://www.ogdengroup.com> www.ogdengroup.com ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
