On Thu, 29 Aug 2013 12:11:32 -0300, Muhammad Gelbana <m.gelb...@gmail.com>
wrote:
But I need to initially store some values and retrieve them later on.
If I inject the *ApplicationStateManager* in the filter and store values
in it, then retrieve these values later on through a tapestry service.
How
will tapestry know which session is currently active ?
The one used in the given thread, supposing the thread is an HTTP request.
Shouldn't I wire the *ApplicationStateManager* service with the request
session id somewhere ?
No.
Also after reviewing the api doc for the *ApplicationStateManager
*service:
http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/ApplicationStateManager.html
What does SSO mean ?
"Responsible for managing *session state objects*, objects which persist
between requests, but are not tied to any individual page or component.
SSOs are also created on demand. SSOs are typically stored in the session,
so that they are specific to a particular client."
Probably the best option for you is to define a per-thread service
wrapping the data you want to pass around instead of putting them in the
session (supposing you don't need to keep this data between different
threads).
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
