2011/7/22 Willy Tarreau <w(_at_)1wt(_dot_)eu>:
You couldn't make DNS SRV mandatory for WS when WS starts with a protocol
upgrade from HTTP which does not mandate use of DNS SRV : the DNS resolving
had to be performed by the HTTP chain well before the connection gets
upgraded to WS. If any existing HTTP component in the chain does not make
use of DNS SRV, everything falls apart.
I understand that the websocket client is *co-located* within the
webbrowser client, but it's a different entity. Nothing prevents it in
using a different DNS mechanism.
Honestly I'm not reading good arguments against DNS SRV for WebSocket
protocol. Perhaps the topic about the HTTP proxies, but there should
be some way to deal with it without forcing WebSocket to inherit all
the limitations and poor capabilities of HTTP (when referring to
scalability and failover).
--
Iñaki Baz Castillo
<ibc(_at_)aliax(_dot_)net>
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf