On Sat, Sep 3, 2011 at 2:43 PM, Willy Tarreau <w(_at_)1wt(_dot_)eu> wrote:
The WebSocket protocol is designed to supersede existing bidirectional
communication protocols which use HTTP as a transport layer to benefit
from existing infrastructure (proxies, filtering, authentication). Such
existing protocols were implemented as trade-offs between efficiency and
reliability because HTTP was not initially meant to be used that way.
WebSocket tries to address all of these goals in the same environment,
and as such is designed to work over ports 80 and 443 as well as to
support HTTP proxies and intermediaries, even if this implies some
complexity specific to these environments. The way it is designed
does not limit it to HTTP and future implementations may make use of
simpler handshake over a dedicated port without revinventing everything.
This last point is important to keep in mind because the traffic patterns
of interactive messaging does not much match standard HTTP traffic and
may induce unusual loads on some components.
+1. I like that phrasing. It summarizes the requirements document pretty
well and also indicates to admins that they may see a change in observed
traffic patterns (in a neutral way).
Joel Martin
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf