Websocket draft-ietf-hybi-thewebsocketprotocol-10

[Vibul Imtarnasan]

Hi,

In doing some surfing around, I found that the webbit web server (based on
netty) has already implemented this.

https://github.com/joewalnes/webbit/tree/0356ba12f5c21f8a297a5afb433215bb2f738008/src/main/java/org/webbitserver/netty

Should we attempt to take the work that has already been done and merge it
into Netty?  The work is published under a BSD license.  If yes, I'll
attempt to contact the authors and see if they wish to take part in this
exercise.


Also, I'm coming around to the thinking that we should support *both *the
existing hixie 75 and 76 as well as the new hybi standard.  The reasons for
this are:

1. Although Chrome and Firefox are upgrading, there is no news for Safari as
yet.

2. There are existing hixie client libraries that are being used in existing
apps.  Netty based apps that rely on this may resist upgrading netty if
hixie is no longer available.  For example, HornetQ.

3. What if there is a new version of hybi in 12 month's time.  We may as
well build in a framework for protocol version management now.


Thoughts?

Regards
Vibul



On 17 August 2011 09:40, 이희승 (Trustin Lee) <trustin at gmail.com> wrote:

> Hi Oli,
>
> Thanks for trying to help us!  I really appreciate that.
>
> I believe the latest draft changed quite a lot from the older ones.  Last
> time I checked, both handshake and frame format were changed.  Therefore,
> the existing handshake code will need a rewrite.
>
> HTH
>
> --
> Trustin Lee <http://gleamynode.net/>
>
> On Wednesday, August 17, 2011 at 3:18 AM, wool.in.silver wrote:
>
> Hi Trustin / Vibul,
>
> I would agree that there is no need to retain support for the older
> Hixie-76
> version of the protocol, as (for example) Chromium 14 seems to have dropped
> support for that version.
>
> I can perhaps help with testing any new implementation. My organisation is
> using Netty to develop WebSocket applications; we see that to support
> Chromium 14 (and apparently Firefox 6) we will need code changes. Probably
> we will not support earlier browsers due to security concerns with earlier
> versions of the WebSocket protocol.
>
> Am I correct to say that both the handshake *and* framing for WebSockets
> has
> changed in version HyBi-10? Where would changes need to be made to Netty -
> it is confined to the handshake method and the
> WebSocketFrameDecoder/Encoder
> classes I believe?
>
> Yours,
> Oli
>
> --
> View this message in context:
> http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Websocket-draft-ietf-hybi-thewebsocketprotocol-10-tp6672115p6692350.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>
>
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20110817/1ea3c5a0/attachment.html