Yes indeed. Look at the header in AtmosphereObjectFactory.java :)
-Norman
> On Oct 27, 2016, at 4:18 PM, Lance Java wrote:
>
> I'm guessing it's similar to this?
> https://github.com/uklance/tapestry-atmosphere/blob/master/tapestry-atmosphere/src/main/java/org/lazan/t5/atmosphere/services/Tapes
I'm guessing it's similar to this?
https://github.com/uklance/tapestry-atmosphere/blob/master/tapestry-atmosphere/src/main/java/org/lazan/t5/atmosphere/services/TapestryAtmosphereObjectFactory.java
On 27 Oct 2016 9:12 p.m., "Norman Franke" wrote:
> I wanted to create a web chat application. I ba
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 clien
I'll try tapestry-atmosphere, I had a quick look over demo code and it looks
slick.
I think this or similar ought to be a core feature or at least a proper
tapestry sub project. It would definitely make tapestry more appealing for
today's SPAs and mobile apps.
John
Sent from my iPhone
> On
That sort of swappable implementation would fit right in with the swappable
JavaScript framework for sure!
I saw some discussion related to whether Prototype support should be
dropped as a default as per Howard's past wishes on the dev boards. It made
me think that perhaps the different js framewo
I'd love to see tapestry support websockets out of the box, perhaps with a
swappable implementation (atmosphere, socksjs, cometd etc)
I've tried to uphold the "tapestry philosophy" in both implementations
using event-handlers, blocks and zones (they're actually a pushTarget
rather than a zone). If
I've been meaning to have a go with Lance's tapestry-atmosphere - seems
very straightforward especially for teams with little time to roll their
own!
Kalle + Cezary - (if feasible - licenses, projects etc.) would it not be
worth all of us jumping on Lance's library (for plugging in Atmosphere) and
It's relatively simple like Cezary says. The only potential issue is with
authenticating JSR 356 websockets, which may require a bit of gymnastics
depending on your needs. If you are using sessions, you can fetch
underlying (servlet) session from the handshake request (see
http://stackoverflow.com/
There's a chat demo in both tapestry-atmosphere and tapestry-cometd
Atmosphere
Demo: http://t5atmosphere-lazan.rhcloud.com/
Source:
https://github.com/uklance/tapestry-atmosphere/tree/master/tapestry-atmosphere-demo
Cometd
Demo: http://t5cometd-lazan.rhcloud.com/chat
Source:
https://github.com/uk
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
10 matches
Mail list logo
