Additional headers in WebSocket draft (Was: Re: Netty 3.2.0.ALPHA3 release: Web Sockets and higher performance)

["이희승 (Trustin Lee)"]

Hi Puran,

Thanks for the heads up.  I didn't know they added new headers to the draft.

According to the draft, handshake became a little bit more complex, but
it's still trivial to handle it.  Even without modifying Netty, you can
implement the new handshake mechanism by modifying the example.
However, I think we could add a simple utility that helps the generation
of a WebSocket request or response.

Cheers,
Trustin

On 06/20/2010 07:49 AM, puran wrote:
> 
> Hi Trustin,
> 
> I am using Netty for my project http://jwebsocket.org, but based on
> WebSocket Protocol version 76 there are few new headers which Netty doesn't
> support yet. Now the new handshaking request from the client looks like
> this:
> 
> 
> GET /demo HTTP/1.1
>         Host: example.com
>         Connection: Upgrade
>         Sec-WebSocket-Key2: 12998 5 Y3 1  .P00
>         Sec-WebSocket-Protocol: sample
>         Upgrade: WebSocket
>         Sec-WebSocket-Key1: 4 @1  46546xW%0l 1 5
>         Origin: http://example.com
> 
>         ^n:ds[4U
> 
> Do you know by when we will have this support?? or i can submit the patch if
> you want. 
> BTW only chrome supports this header in terms of browser.. let me know what
> do you think??/
> 
> Regarsd
> 
> 

-- 
what we call human nature in actuality is human habit
http://gleamynode.net/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 293 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/netty-users/attachments/20100621/25464a80/attachment.bin