Re: (Server-independent) Comet support in Wicket?
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]
Re: (Server-independent) Comet support in Wicket?
Jörn Zaefferer wrote: 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? http://people.apache.org/~tobrien/wicket/apidocs/org/apache/wicket/ajax/AjaxSelfUpdatingTimerBehavior.html I've never used it. But I guess you'll just do something like: Component p = new MyPanel(mypanelid); add(p); p.setOutputMarkupId(true); p.add(new AjaxSelfUpdatingTimerBehavior(Duration.seconds(2)); The component will now re-render itself every 2 seconds. 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. Yes, that would be essential (as with any framework). Important reads: http://people.apache.org/~tobrien/wicket/apidocs/org/apache/wicket/protocol/http/pagestore/DiskPageStore.html http://www.nabble.com/DiskPageStore-improvements-for-1.3.1-p14711582.html http://cwiki.apache.org/WICKET/wicket-inside.html I did not yet find a link that explains what Wicket puts in the session. But basically (in Wicket 1.3) it is the entire component tree instance of the last page that was rendered to the user (including all model instances, but excluding data in detachable models). Nothing else goes to the session. The page does not go the session when it includes bookmarkable links only (which is very rare). Another use case that is supported is login forms. (For both: look up stateless pages). 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]
Re: (Server-independent) Comet support in Wicket?
wicketstuff-push might be what you are looking for: wicket cometd support with jetty. but i don't think that anybody has used it with 10k simultaneous users yet. see: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push/ https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-push-examples/ Jörn Zaefferer-2 wrote: Hi, I've started evaluating Wicket today for an application written from scratch. First impressions are very well, there is just one requirement on which I couldn't find enough useful information yet: Comet support in Wicket or Comet with Wicket. Before looking at Wicket I tried to use lift which has Comet support built in (based on Scala Actors). This post (http://blogs.webtide.com/gregw/2006/07/25/1153845234453.html) suggests that its not possible to implement scaleable Comet support within a web framework, instead it must be supported by the application server, eg. Jetty 6. Post about Comet and Wicket, eg. this one (http://www.mail-archive.com/[EMAIL PROTECTED]/msg17308.html) don't give me any actual information about the current state of afairs (its from 2006, the linked sf.net issue is now private). This issue (http://wicketstuff.org/jira/browse/DOJO-23) about integration with cometd isn't too helpful either, I can't find any documentation on that. To provide some information on the actual requirements I have: 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. While the exact number of simultaneous users isn't clear yet, up to 10k must be possible with the appropriate hardware. Thanks Jörn Zaefferer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - --- Stefan Fußenegger http://talk-on-tech.blogspot.com // looking for a nicer domain ;) -- View this message in context: http://www.nabble.com/%28Server-independent%29-Comet-support-in-Wicket--tp15574656p15589149.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: (Server-independent) Comet support in Wicket?
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]
