3 ms·
> Why should HTTP be a multiplex protocol though; that's the issue. Because HTTP is inefficient due to the TCP three-way handshake, and because pipelining has
by FooBarWidget 13y ago
> Why should HTTP be a multiplex protocol though; that's the issue.
Because HTTP is inefficient due to the TCP three-way handshake, and because pipelining has many problems. These are fixed by multiplexing.
> So why not just use SSL/TLS? Why wrap it into the HTTP protocol?
They are using TLS.
- jimktrains2 13y ago> Because HTTP is inefficient due to the TCP three-way handshake, and because pipelining has many problems. These are fixed by multiplexing. So why should HTTP care about this? > They are using TLS. But it's specified as part of the HTTP protocol