Re: [hybi] Multiple connections serialization and proxies

[Jamie Lokier <[e-mail]>]

Thomson, Martin wrote:
> App A establishes WS connection to example.com with sub-protocol foo.
> 
> App B requests WS connection to example.com also, but with sub-protocol bar.  It cannot signal this sub-protocol use to example.com if it re-uses the connection established by App A.
> 
> Similarly, if App A establishes state on the connection (for example, using one of the BWTP channel headers), then this state could interfere with state that B attempts to establish:
> 
> App A logs in and sets the user name to 'alice'.  App B logs in and sets the user name to 'bob'.  Are requests that follow authorized based on alice's permissions, or bob's?
> 
> Keep in mind that applications will assume that this 'connection' is theirs to use.  In many cases, the connection will be dedicated, and will persist, so how will the proverbial 'inexpert' server developer know how to cope with an unexplained error like this?
> 
> This is made even worse if an intermediary attempts (legitimately) to multiplex streams...

All of that is moot provided the reuse/multiplexing is done properly.

That is, with application-visible properties such as sub-protocol
being per virtual connection, not per real connection.

Inexpert server authors (and client authors) will not negotiate these
features, and won't have to deal with it.

-- Jamie