Hello, This to me seems like a one way ticket to deadlock-land. Unless you're able to define a strict lock hierarchy and always acquire locks in the same exact order, this option will be extremely difficult for application developers to use correctly.
Just my 2 cents. Cheers, Nelson. On 18/01/2013, at 11:11, Thiago H de Paula Figueiredo <thiag...@gmail.com> wrote: >> 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? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
