I've successfully used Atmosphere with tapestry, though I remember that setup wasn't trivial, but once you do it -- it works well. Atmosphere provides access to its broadcasters using static factory methods, so you can get them from whenever you need. Also I used atmosphere requests interceptors by contributing to tapestry MasterDispatcher to pass tapestry context (like current authenticated principal, or tapestry registry instance) to atmosphere through the request attributes.
Things may changed with Atmosphere because it evolved a lot after I used it. But when I simply need to call tapestry services from client-side javascript I prefer using tynamo-resteasy. Of course in this case you don't get web sockets support. On Fri, Aug 16, 2013 at 9:09 AM, Martin Kersten <martin.kersten...@gmail.com > wrote: > Hi there, > > back in the old days I used to use GWT alot in conjunction with > Tapestry. Nowadays it would be fine to develop using JS at the Client side > and I want to use Tapestry at the backend. > > I would love to use something like socket.IO directly within the > JS-client-code so I investigated the Atmosphere (github) package. Saidly > there is no direct implementation nor support for the Tapestry world. And > it looks like I would loose a whole weekend trying without a guarantee that > I come up with something good. > > Currently implementing Atmosphere I would go for a > HttpServletRequestHandler, warp the Tapestry servlet or even alter it > directly (so I can use the default Atmosphere servlet based on the accessed > page and so on. The way I used to implement GWT by creating a Page writing > http directly using a MarkupWriter seams not to be that feasable since > Atmosphere has a bunch of things to do, I dont understand right now. > > So I would love to know what is the current preferred way to use something > like the socket.io lib in conjunction with Tapestry as the serving > backend? > > > Thanks for reading, > > Martin (Kersten), > Germany > -- Dmitry Gusev AnjLab Team http://anjlab.com
