Reading <<Wicket in Action>> to learn Wicket, I understand that sessions are
not thread-safe. I have the following questions about a Wicket app:
1. If I open another tab on the same browser (IE or FF), visitor activities on
the same Wicket app are considered in the same session?
2. If I start IE or FF in another window, visitor activities on the same Wicket
app are considered in the same or different session?
3. If dirty() is called within a method of custom session object, then it is
the developer's responsibility to implement dirty() to synchronize with other
clustered web servers, correct?
Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
