Also take a look at: http://jfarcand.wordpress.com/2010/10/07/writing-websocket-application-using-apache-wicket/ https://github.com/jfarcand/atmosphere/tree/master/samples/wicket-clock/ <http://jfarcand.wordpress.com/2010/10/07/writing-websocket-application-using-apache-wicket/> https://github.com/martin-g/wicket-atmosphere-tests
On Fri, Nov 12, 2010 at 4:49 PM, jcgarciam <[email protected]> wrote: > > Josh, what monzonj saids is valid. > > When doing ajax operation in wicket, you can't trigger other ajax operation > in parallel that change the component tree because it will get block until > the first operation finishes. > > But having said that, you need to consider that web browser limits the > amount of http request you can make to a single host (vary from 2 to 8 i > believe) which mean you can't have either a lot of ajax component doing > poll > at the same time. > > On Fri, Nov 12, 2010 at 12:43 PM, Josh Kamau [via Apache Wicket] < > [email protected]<ml-node%[email protected]> > <ml-node%[email protected]<ml-node%[email protected]> > > > > wrote: > > > I have implemented an application that alerts the user on various events. > I > > > > created a notification's bar at the top of my page. This bar has a panel > on > > > > which i added AjaxSelfUpdatingTimerBehavior. The Panel is available in > all > > > > pages. whatever the page the use is, as long as the panel is rendered, it > > polls the server on regular intervals and displays notifications for > > various > > events - the facebook style. This is one of the features that has made > me > > stick with wicket. > > > > regards. > > Josh > > > > > > 1. > > > > > http://wicket.apache.org/apidocs/1.4/org/apache/wicket/ajax/AjaxSelfUpdatingTimerBehavior.html > > > > > > On Fri, Nov 12, 2010 at 10:37 AM, Frank van Lankvelt < > > [hidden email] <http://user/SendEmail.jtp?type=node&node=3039773&i=0>> > > wrote: > > > > > On Fri, Nov 12, 2010 at 3:55 PM, José Monzón <[hidden email]< > http://user/SendEmail.jtp?type=node&node=3039773&i=1>> > > wrote: > > > > I recently run into a problem that has make me consider whether > > > > continuing using Wicket or not for a project. I hope guys you can > > > > throw some light into it. > > > > > > > > I need to create a web application that uses ajax to keep itself > > > > udpated while still allows the user interact with it also using Ajax. > > > > Imagine something as GMail, Documents, Facebook, Twitter, etc. > > > > > > > > On this pages, is very common to have some ajax COMMET, long polling > > > > or also known as inverse AJAX to keep the page updated. But that > > > > doesn't prevent the user to click here and there and update the page > > > > also using AJAX. They are independent XMLHttpRequest with a browser > > > > can handle perfectly. > > > > > > > > I was thinking about doing this on Wicket, but apparently it's > > > > impossible by design: > > > > https://issues.apache.org/jira/browse/WICKET-2437 > > > > > > > > Page objects aren't thread-safe and wicket will block any other > thread > > > > (AJAX call) that tries to access the page while another request (for > > > > instance our long poll) is there. > > > > > > > > Have you ever find yourself into this kind of problem? What's the > > > > workaround if any? > > > > > > > the comet-like functionality is useful for things like chatting, but > > > you wouldn't > > > need access to the page for that as you're unlikely to change the > > > component tree. > > > > > > The alternative to long polling is, of course, regular polling. Queue > > > the events > > > and process them when a request is processed. Then you can access the > > > page, > > > update the component tree and rerender the relevant parts. > > > Maintaining the queue > > > is a bit tricky, as one has to make sure that it doesn't grow too > > > large and it must be > > > disposed of properly. > > > > > > We've used this method to implement a single-page-application that > > updates > > > exclusively with ajax. It's not in the facebook/google/... range, but > > > it works well > > > enough for our purposes. > > > > > > cheers, Frank > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [hidden email]< > http://user/SendEmail.jtp?type=node&node=3039773&i=2> > > > > For additional commands, e-mail: [hidden email]< > http://user/SendEmail.jtp?type=node&node=3039773&i=3> > > > > > > > > > > > > > > > > > > > > -- > > > Hippo > > > Europe • Amsterdam Oosteinde 11 • 1017 WT Amsterdam • +31 (0)20 > > 522 > > > 4466 > > > USA • San Francisco 185 H Street Suite B • Petaluma CA 94952-5100 > > > • +1 (707) 773 4646 > > > Canada • Montréal 5369 Boulevard St-Laurent #430 • Montréal QC > > > H2T 1S5 • +1 (514) 316 8966 > > > www.onehippo.com • www.onehippo.org • [hidden email]< > http://user/SendEmail.jtp?type=node&node=3039773&i=4> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [hidden email]< > http://user/SendEmail.jtp?type=node&node=3039773&i=5> > > > For additional commands, e-mail: [hidden email]< > http://user/SendEmail.jtp?type=node&node=3039773&i=6> > > > > > > > > > > > > ------------------------------ > > View message @ > > > http://apache-wicket.1842946.n4.nabble.com/Wicket-design-incompatible-with-Web-2-0-tp3039707p3039773.html > > To start a new topic under Apache Wicket, email > > [email protected]<ml-node%[email protected]> > <ml-node%[email protected]<ml-node%[email protected]> > > > > To unsubscribe from Apache Wicket, click here< > http://apache-wicket.1842946.n4.nabble.com/template/TplServlet.jtp?tpl=unsubscribe_by_code&node=1842946&code=amNnYXJjaWFtQGdtYWlsLmNvbXwxODQyOTQ2fDEyNTYxMzc3ODY= > >. > > > > > > > > > -- > Sincerely, > JC (http://www.linkedin.com/in/jcgarciam) > Work smarter, not harder!. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-design-incompatible-with-Web-2-0-tp3039707p3039794.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
