On Thu, 2011-09-15 at 01:10 -0700, Rajiv Mordani wrote:
> Hi All,
> Before coming up with an API for WebSocket I wanted to have a
> discussion around what the use cases are for what we want to support
> in the servlet API. Here are some thoughts I have - but want to get
> input from the expert group and see where we need to take the API.
>
> * Support for upgrading protocol to WebSocket
Besides this, I don't understand how this is not out of scope. The rest
is about specifying WebSocketServlet, and for example we don't do
SIPServlet (which has the exact same reqs list).
I would support revising the JSR to state that we're also going to
specify javax.servlet.websocket.WebSocketServlet (essentially stating
that we'll be doing all *Servlet that are web related in the future),
but the schedule would need to be adjusted (early draft in Q3 11 does
not sound realistic - actually it's not realistic even without it I
believe).
> * Support for messaging constructs that WebSocket has in the
> Servlet API
> * Container requirement to support data framing - not exposed to
> the user in the servlet API
> * Support for security constraints, authentication and
> authorization
> * Support for exposing the sessions, cookies and other java ee
> constructs like user transaction etc in a websocket
> application
> * Add enough support in the servlet API to be able to build a
> higher level WebSocket API (for example like what we did with
> JAX-RS).
> What else am I missing? If there are other requirements, use cases
> that people think need to be addressed, please let us know.
Websocket allows mixing byte and char (a byte message can follow a char
message, etc). This should have implications in the API.
--
Remy Maucherat <rmaucher_at_redhat.com>
Red Hat Inc