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

[Maciej Stachowiak <[e-mail]>]

On Feb 3, 2010, at 7:51 AM, Pieter Hintjens wrote:

> On Wed, Feb 3, 2010 at 3:10 PM, Greg Wilkins <[e-mail]> wrote:
> 
>> I don't think you can assume that most websocket using software
>> and/or subprotocols will have the same developer working on
>> the client side and the server side.
> 
> I've never seen a protocol that makes this assumption and it is a
> quite extraordinary one from the perspective of interoperabilty.
> 
> Ian, could you elaborate please?  I do not understand your intention
> in making this statement, nor how significant it is to implementing
> WebSocket.

The likely deployments of WebSocket are going to be one of these:

JavaScript code running in a browser --> browser's WebSocket implementation ====> WebSocket service that directly implements the protocol

JavaScript code running in a browser --> browser's WebSocket implementation ====> generic WebSocket server --> service code


Ian is saying that he thinks the JS code running in the browser and the specific WebSocket service are likely to be created by the same entity on some level, and he apparently thinks it is likely that many WebSocket services will implement the protocol directly rather than use any kind of framework or standard server. Note though that the browser code that implements the client side of the WebSocket protocol will almost never be written by the same party. Also, if the WebSocket service accepts cross-site connections, the assumption will not be true at all.

Regards,
Maciej