The C for RFC in short - What's the point ?<p>I really don't understand what problem this draft solves, and the draft doesn't seem to explain it coherently.<p>It effectively describes just another layer on top of TCP that implements its own addressing, loosely follows HTTP syntax and utilizes TLS for security. The application still needs to implement yet another layer to deal with the data carried by this protocol. So instead of using (TLS + application protocol) combo, the app needs to use (TLS + WS + application protocol).<p>So what's the point in making this protocol a standard ?<p>-- PS --<p><i>Historically, creating an instant messenger chat client as a Web application has required an abuse of HTTP to poll the
server for updates while sending upstream notifications as distinct HTTP calls.</i><p>Perhaps that's how they do it at Google, but <i>historically</i> applications like httptunnel simply opened exactly two persistent HTTP connections - one with a very long POST and the other one with a very long GET - and used them to send data up and down respectively.