On Fri, 18 Jan 2013 05:24:24 -0200, Ulrich Stärk <u...@spielviel.de> wrote:
I find this change has too extensive imiplications as to default it to true.
Agreed.
Also, I find it much to coarse-grained to either enable it for the whole application or for nothing.
Agreed too. It seems it's a lock on the whole session (am I right?), something that doesn't make sense at first to me. When two different threads accessing different attributes in the session at the same time, none should be blocked. Why not a lock per session attribute? Or per @Persist field or @SessionState type?
An annotation on event handlers that require synchronized access to the session is the way to go IMO.
That would be nice. -- Thiago H. de Paula Figueiredo --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
