Howard Lewis Ship wrote: > The solution I've > been thinking of will have some pretty wild performance effects, as > requests that share sessions will need to be routed through a single > lock object, stored in the session. >
I hope it wouldn't hold the lock for the entire request... Sometimes you need access to the same session object from multiple requests at the same time (eg. if you have a single long running request and another request to poll it to get progress). That said a lock would be nice sometimes to stop the session variables getting clobbered by competing requests. You could just have write locks, only allow 1 writer at a time but many readers :)... Anyway, this may be completing unrelated to what you were thinking :). -- View this message in context: http://tapestry.1045711.n5.nabble.com/Backfixes-for-5-2-6-tp4512055p4516113.html Sent from the Tapestry - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
