Re: [hybi] Handshake was: The WebSocket protocol issues.

[Alexander Voronin <[e-mail]>]

To my mind is enough to send 101 or 501 if websocket is not implemented on
server or intermediary. You are making things too complicated and implicit.

2010/9/24 Simone Bordet <[e-mail]>

> Hi,
>
> On Thu, Sep 23, 2010 at 21:06, Greg Wilkins <[e-mail]> wrote:
> > The upgrade response does not need to wait for any non-HTTP data, so
> > there is less potential for blocking. The server can send the ping
> > (which may fail if an intermediary closes the connection on the 101)
> > and then immediately start sending application ws frames while waiting
> > for the pong.   The client has to wait for the 101 as it does already,
> > and then it can wait for the ping as well.    I assume it already had
> > a timeout for the 101 response, so this should not be any extra
> > complexity.
>
> Just for sake of clarity, if an intermediary discards the websocket
> bytes because it does not understand them, but does not close the
> connection, the websocket client will receive the 101 but not the
> server ping, so the client waits a timeout before closing itself the
> connection, right ?
>
> The server can then assume that all the data it sent after the ping
> was lost because it did not receive the client pong.
>
> +1 for me also on this handshake.
>
> Simon
> --
> http://bordet.blogspot.com
> ---
> Finally, no matter how good the architecture and design are,
> to deliver bug-free software with optimal performance and reliability,
> the implementation technique must be flawless.   Victoria Livschitz
>



-- 
когда я опустился на самое дно, снизу мне постучали..