Brian Dinsmore wrote: > my issue is that the process on the server normally > completes by writing the results of it processing to the user's session > which is ultimately used to drive what is seen on the page when they hit > our custom "refresh" button...
It doesn't matter that the you put the data in the session. You can still periodically write a null byte to the client. Sending a null byte doesn't show anything on the client, all it will do is check the socket connection. If you wait to check this connection after you're done with your processing, then you're not saving anything. -- Michael Peters Developer Plus Three, LP _______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
