On Feb 16, 2010, at 4:37 PM, Justin Lee wrote:
> This morning I committed basic support for websockets to the trunk.
> It's located in modules/websockets and is more or less ready to be
> played with. There are a few basic unit tests included. Probably
> the most interesting is WebSocketFilterTest.testSimpleConversation.
> It's a servlet-based approach in which the servlet is largely
> unaware of the underlying websockets work. This works well enough,
> but it does impose a slight burden on the servlet author. This
> attempted complete transparency does lead to a little bit of
> awkwardness in use, however.
>
> So now that it's working, we'll be doing some work on the API itself
> to provide a cleaner way to register your components for use in a
> websockets conversation.
Great stuff.
> So please play with it and give some feedback. We'd like to have a
> nice, clean API we can all live with so if you have any input now's
> the time. I'll be looking over what jeanfrancois has done with
> atmosphere and jetty to see how much we can borrow
I guess it depends on what you mean by "borrow" w.r.t. atmosphere. If
it means copy from atmosphere then i would strongly suggest not and
instead lets integrate with atmosphere, making changes as appropriate
either way, as there is way more value in doing that. Especially at
the higher level such that JAX-RS and Jersey can be leveraged and
utilized with many useful Atmosphere features.
Paul.
> . Any suggestions are completely welcome. I want this to be useful
> and usable for someone other than myself. :)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>