I'm currently evaluating component based frameworks, as we are currently using Wicket, and one of the problems we encounter is Ajax interactions after the http session has expired.
If a user clicks on a component that is Ajax enabled - the framework throws a PageExpiration exception. For most applications, we want the request to still continue on as normal. The HelloWorld example from Tapestry doesn't appear to experience this. My questions are - For persistent data on a page where is this serialized to? - Are all Ajax interactions safe in this manner, form buttons, links, etc -- View this message in context: http://tapestry.1045711.n5.nabble.com/Session-Expiration-Ajax-tp5719213.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
