It works different. Johan synchronizes on the session, so two users have their requests executed without this. The problem occured when one user (one session) refreshed quickly.

So, as the synchronizations happens for a session, the scalability is not reduced.

Eelco

Gili wrote:

On Wed, 5 Jan 2005 15:17:59 +0100, Juergen Donnerstag wrote:



Hi Eelco,



Syncronized around session object in HandleRender so that only one request can touch/render a page and its components.


I think I understand the change, but is there a possibility that it
could ever happen and thus requires synchronization?



It can if two users hit a Page at the same time (I think). Thing is, I think that synchronizing Page rendering by default isn't necessarily a good thing. It simplifies things but it'll also reduce the scalability of Wicket.

Gili





-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to