Remy, Greg,
You'll are both right to some extent about the kind of support we
are thinking of adding in this release of the spec for websockets. I
think at a minimum we need to add support for the protocol upgrade and
in a generic way. I think we can do a little more than that. However I
don't think we will add a comprehensive API for websocket in this
release of the spec. We have a lot of things to achieve in this release
and some of the things that are of higher priority IMHO like PaaS
support(main theme for Java EE 7) and NIO2 for example. However we do
have to have some APIs for websockets that we can build upon in a future
spec just like we did with async in 3.0 that I hope we can improve upon
in this release of the spec.
- Rajiv
On 5/27/11 12:32 AM, Remy Maucherat wrote:
> On Fri, 2011-05-27 at 08:21 +1000, Greg Wilkins wrote:
>> I make no representations that this is the best way to proceed, or
>> even a good way... it is just how we have done it so far. Users have
>> been warned that significant changes to this API are likely.
> Besides the upgrade mechanism, this has not been mentioned as being in
> scope for this JSR. Which is quite understandable IMO, it's a lot of
> spec work on something that is not finalized yet.
>