Dojo seem's to provide an API that looks like WebSocket, and fallback to other techniques if WebSocket isn’t available. http://www.sitepen.com/blog/2010/10/31/dojo-websocket/
If you want to provided a real bi directionnal data channel between your server and your client, you will need a gateway that can manage protocoles like -cometd, -flash (rtmpt protocole), - ajax long polling - websocket Kaazing provided this kind of gateway and they say ( http://tech.kaazing.com/documentation/faq.html#bayeux "Most Comet implementations rely on the Bayeux protocol, which requires messages from the origin to be transformed to conform to the Bayeux protocol. This transformation introduces unnecessary complexity in your system, requiring developers to manipulate one message format on the server (for example, JMS, IMAP, and XMPP) and a second message format (for example, Bayeux or JSON) on the client. Bayeux also introduces an unnecessary performance overhead to your system by forcing a message to be interpreted and processed prior to being sent over the wire. With WebSocket, the message sent by the server is the same message that is delivered to the browser, eliminating the complexity and performance concerns introduced by transformation code." We use the same approach for our gateway. We also feel like WebSocket will replace cometD even if we don't know IE9 status about WebSocket. 2010/11/7 Alessio Gambi <agamb...@gmail.com> > I used the DWR 2.0 and it worked fine. > But I did not really liked the solution for some reasons: > - you need to add the DWR servlet along tapestry and do some "tricks" to > forward the dwr calls to it while tapestry maintains the state of your > application. > - the solution was too *framework specific* while it should be better to > have some generic service and different implementations.(like prototype for > js as an example) > - DWR is mainly about implementing RPC with JavaScript and the "reverse > Ajax" is only one of its features. I do not known if it so right to "import" > the entire framework just to have it. > > -- Alessio > > On 7-nov-2010, at 04:22, "Robert R. Sanders" <robert.sand...@ipov.net> > wrote: > > > I would think some integration for a high/medium level framework like > atmosphere, or the dojo CometD api could potentially avoid tying T5 to a > specific server. > > > > On 11/6/2010 7:11 PM, Howard Lewis Ship wrote: > >> Not at this time, perhaps in 5.3. I know I'd use that capability if it > was > >> available, even if it tied Tapestry to Jetty specifically. > >> > >> On Sat, Nov 6, 2010 at 4:27 PM, Halil Karakose<halilkarak...@gmail.com > >wrote: > >> > >>> Hi, > >>> I found that tacos supports cometd for tapestry 4. What about tapestry > 5? > >>> Does tapestry support cometd? > >>> > >>> thanks > >>> > >> > >> > > > > --------------------------------------------------------------------- > > 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 > >
