Short answer: Forms, buttons, links and ajax actions in general do not require the session. You can do whatever you like in your ajax actions which *might* include accessing session state (eg via @Persist). There are a couple of core tapestry components that require the session but it's your choice to use them or not.
Long Answer: Unlike wicket, tapestry does not require the session for component rendering. Tapestry pages and components are singletons. Tapestry performs a bit of a magic trick to transform page and component classes such that any request specific variables are written to and read from a thread local map. It's possible to create tapestry apps which never use the session and are able to use the URL to pass any id's etc required to lookup entities from the database etc. When a form is posted, the data used to render the form is serialized to a hidden field which is used to re-hydrate the data when the form is posted. In most cases, only the database id's are used. This recent thread discusses striving for zero session persistence where possible: http://tapestry.1045711.n5.nabble.com/Appropriate-recommended-usage-for-Persist-in-components-td5719116.html -- View this message in context: http://tapestry.1045711.n5.nabble.com/Session-Expiration-Ajax-tp5719213p5719214.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
