Lance, thanks again, i will check the docs. Seems that longpolling or jsonp is supported best by servers and browsers.
The first question i will have if there is a kind of client identification built in. The chat messages must be propageted to the correct users and not to all users. Is a client identification part of the project or does this completely depends on my own businesslogic? Kind regards David On 23.05.2013 09:44, Lance Java wrote: > tapestry-cometd is built using the cometd integration in atmosphere. > Atmosphere supports a variety of push mechanisms including WebSockets, > Server Side Events (SSE), Long-Polling, HTTP Streaming (Forever frame) and > JSONP. > > Out of the box, tapestry-cometd is configured to use > org.cometd.websocket.server.WebSocketTransport but this can be configured > in your AppModule ( > https://github.com/uklance/tapestry-cometd/blob/master/src/main/java/org/lazan/t5/cometd/services/CometdModule.java#L54 > ) > > The supported servers and browsers are listed here: > https://github.com/Atmosphere/atmosphere/wiki/Supported-WebServers-and-Browsers > > Some more docs here > https://github.com/Atmosphere/atmosphere > https://github.com/Atmosphere/atmosphere/wiki/Getting-started-with-Cometd > https://github.com/uklance/tapestry-cometd/wiki/Configuring-the-CometD-Servlet > http://cometd.org/ > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
