Jörn Zaefferer wrote:
... The
architecture must support several both dependent and independent
components on a single page which get updated based on server-events,
be it on schedules or events triggered by other users.
Wicket currently support updates through timers on the client side.
While the exact
number of simultaneous users isn't clear yet, up to 10k must be
possible with the appropriate hardware.
That is quite huge, for any framework. Because of the way Wicket uses
the HTTP session, you are probably best of with a Terracotta cluster.
Regards,
Erik.
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
