Rajiv.
Oh cool... should have read this before responding to Remy.
Makes sense for the servlet API to avoid trying to solve all of the WS
API issues and instead just focus on how to well handle the initial
upgrade request and then pass control to some other specification.
Note that I'm not that keen on allowing applications to handle the
upgraded connection. I'd like to see that containers are still
responsible for whatever protocol is upgraded to. So we need a way
to expose the upgrade HTTP request to the servlet together with
knowledge of what target protocols the container supports.
cheers
On 8 October 2011 05:31, Rajiv Mordani <rajiv.mordani_at_oracle.com> wrote:
> Hi All,
> After some internal discussions around WebSockets we have come to the
> conclusion that for Servlet 3.1 spec we will target only the upgrade portion
> of the specification. We intend to file a JSR soon targeted for WebSocket
> itself as the protocol which will address the issue of WebSockets in the
> Java EE platform. When we do file the JSR I will let the EG know so that
> those interested in participating in the JSR can join the expert group for
> the JSR.
>
> In the meantime Shing Wai has been working on a proposal for upgrade support
> in the Servlet API and is working out some issues based on feedback received
> internally and will send to the EG soon.
>
> - Rajiv
>
>
>