I wanted to create a web chat application. I based it off of Atmosphere (http://async-io.org). I made a small contribution to that project to make integration with Tapestry easier (primarily for IoC.) It was enough to get it working for me. Atmosphere provides a nice JavaScript API for the client side and can fall back to pre-WebSocket technologies.
-Norman > On Oct 26, 2016, at 4:39 PM, Cezary Biernacki <cezary...@gmail.com> wrote: > > Hi John, > I am working on an application that uses both Tapestry and WebSockets. The > integration is quite easy. Write your endpoint class as a normal service, > so you can inject/request your other Tapestry-based services in usual way. > Then in your AppModule add startup method (see @Startup annotation), that > just register your websocket handling services in whatever websocket stack > you are using (we use Jetty's WevSocketServlets). > > Cezary > > > On Wed, Oct 26, 2016 at 8:16 PM, Qbyte Consulting <qbyteconsult...@gmail.com >> wrote: > >> I want to develop a tapestry chat component that uses a WebSocket to handle >> real time text messages. I need to integrate so that users can see who is >> logged in to the Tapestry app. >> >> How would I make a class in a Tapestry app a WS endoint that can also >> access my apps Tapestry services as well as handle the WS client? >> >> John >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
