This does not seem to have gone through the first time. Resending.
- Rajiv
-------- Original Message --------
Subject: WebSocket requirements
Date: Thu, 15 Sep 2011 01:10:57 -0700
From: Rajiv Mordani <rajiv.mordani_at_oracle.com>
To: jsr340-experts_at_servlet-spec.java.net
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
* 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.
Thanks
- Rajiv