On Feb 20, 2008 3:50 AM, Erik van Oosten <[EMAIL PROTECTED]> wrote: > 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.
Can you point me at a resource that provides some details on that? > > > 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. To that regard: Is there a document that describes Wicket architecture? It looks like I need a good understand of the session usage when dealing larger number of users. Thanks Jörn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
