Hi,

a couple of weeks ago, we had an issue with our application when all assets 
were checked by our AccessControlDispatcher which is checking User permissions 
to access any resource based on user information stored in a session state 
object . The problem was that the session-state-objects were somehow dropped 
(new sessions were created) when multiple request threads were accessing at the 
same time.
We could solve this for most cases by simply not checking access on static 
assets. Which is OK.
But now we discover that the problem somtimes occurs on pages where multiple 
dynamic images are rendered by the Tapestry Application. Those images are 
passed through the access control dispatch which in turn checks access 
permission as above (with the session object) which can cause sessions to be 
dropped when it happens from multiple request threads at the same time.

Is this a design problem with my application that multple threads can access 
the sessionstateobject at the same time and thus break its uniqueness or is it 
tapestrys fault that it does not prevent it from breaking?
What can I do to resolve this?

Thanks

Moritz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to