Hi, It happened to me again that one of my RequestFilters was creating a SessionStateObject. Which, when done for all assets of a page simply fails at one point. Different Threads accessing different Assets in parallel start to create new Sessions and thus the SSO gets lost. Now one can resolve this by putting all RequestFilters that use the SSO behind the StaticFile filter. But since it is not enforced by Tapestry, other people might stumble over this. Can't this be made "thread safe" in some way? So that it would be OK to have multiple parts of the page be handled by different threads using the same SSO?
Regards Moritz --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
