Brian Dinsmore wrote: > so i forgot one detail... while the "cancel-able" process is running, > the user can navigate around and do whatever else they want, except > kicking off an additional "cancel-able" process. thus, since they could > be kicking off various other servlets, i dont want to stop any of that > processing. the only thing i want to monitor and kill if they hit the > cancel button is the original "cancel-able" servlet processing...
This should still work. Sending back null bytes to the client won't interfere. All it does it check to see if the connection is still there. This null byte will be recieved by the Ajax.Request object that you created for the original operation. > i guess i will start playing around with java threads where one is doing > the processing and a 2nd one is writing NULL bytes to the client until > it bombs. and if and when it bombs, it would interrupt the processing > thread and then the servlet would return... Let us know what you find out. -- Michael Peters Developer Plus Three, LP _______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
