Re: [hybi] Reliable message delivery (was Re: Technical feedback.)

[Salvatore Loreto <[e-mail]>]

just to make order in this particular thread discussion

as I understood, two different problems have been arised

1) "safely" shutdown a websocket connection.
      The possibility to lose data while closing a TCP connection is a 
well-known problem,
      as has also been discussed and described in the thread.

      Some people think there is a value to add to the spec gracefully 
shutdown the websocket connection.

      However I haven't seen a clear consensus on it.

      So please if you have an opinion on this, speak up!!!


2) what happen if/when the connection is lost; this can happen for 
several different reasons:
    e.g. a NAT restarting, the mobile terminal go out of network 
coverage etc.

     here we have different sub problems in my opinion:

     2.1) how detect as fast as possible that the connection has been lost

     2.2.) what to do after have reconnected.

     Are those something people think is important to spend cycles on??


cheers
/Sal



On 01/31/2010 01:52 AM, Justin Erenkrantz wrote:
> On Sat, Jan 30, 2010 at 6:49 AM, Jamie Lokier<[e-mail]>  wrote:
>    
>> Orderly close does not help with network-level disconnects, so other
>> techniques like duplicate elimination are valuable too.
>>      
> True, but I think it's important that we - as a group - crawl before we run.
>
> I'd like to see consensus that orderly close is important and should
> be added and how we go about doing so in a sane way.
>
> If we can't even get buy-in for that, then other more advanced
> optimization techniques are likely to go nowhere as well.  -- justin
> _______________________________________________
> hybi mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/hybi
>