Comet is still a very hacky technology stack with no solid / mature infrastructure let alone standards, though HTML 5 will change that. If this doesn't bother you then Jetty and Tomcat both have built in Comet support, though be forewarned that using a reverse proxy has issues and Comet misused has the potential to bring a web server to its knees.
I am using DWR, a decent JavaScript and Comet framework. DWR attempts to compensate somewhat for the fact that web servers are not entirely ready for Comet. If you use Apache in front ->mod_jk (or AJP) to Tomcat, then possibly avoid comet (see: http://www.mbaworld.com/docs/aio.html). If you intend to use standalone Jetty or Tomcat with APR or Nio connector then DWR is worthwhile, I found this out the hard way. Peter ----- Original Message ----- From: superoverdr...@gmx.de To: users@tapestry.apache.org Sent: Sunday, 26 April, 2009 14:41:08 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: HTTP Streaming (Ajax) / Comet Integration What about supporting Comet (http://en.wikipedia.org/wiki/Comet_(programming)) in Tapestry5 ? If you use lots of Ajax on a website, this can slow down everything tremendously...therefore a Comet HTTP Streaming Server that does not disconnect will support lots of simulataneous connections on a single server. Has anyone any experience on Comet in combination with Tapestry5? Thanks! Toby --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
