I've always assumed that there is some kind of synchronization taking place within the web server (tomcat ...) and that server would only process one request from a session at a time.
I don't think the web server does that. There are valid cases when simultaneous connections within a session are needed (e.g. when downloading assets).
Kent Tong posted a link dealing with its issue earlier in this thread: http://www.onjava.com/pub/a/onjava/2004/03/24/loadcontrol.html?page=1
It would be nice if Tapestry provided something similar as a configurable option (probably per page?).
Adding synchronization can be very cpu expensive and if it's unwarranted, then it's a waste of valuable server resources...
Synchronization consumes resources only when there is actual contention but that is precisely when synchronization is needed, so it shouldn't hurt.
regards, Tzvetan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
