This sounds like a push mechanism might be better than refreshing at an interval. I've recently released a beta for a push component based on CometD here https://github.com/uklance/tapestry-cometd
I don't currently have a mechanism for stopping the subscription but it could be added quite easily. I have an outstanding issue (https://github.com/uklance/tapestry-cometd/issues/10) to execute custom javascript when events are published. I'd be interested to hear a bit more about your application to see if tapestry-cometd is a good fit. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Form-getting-resubmitted-after-an-hour-tp5714319p5714322.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org