On Wed, 05 Jan 2005 10:13:19 -0500, 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.
Just rethinking this point. I think our conceptual model is
such that a user can only be one Page at a time and in reality this
isn't what is happening because if you hit REFRESH many times quickly,
the server is still busy rendering a page that the client aborted and
the client would like to see the next page already.
I guess synchronizing on the session object is the right thing
to do from a conceptual level.
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
