Linked by Thom Holwerda on Wed 25th Jan 2012 22:05 UTC, submitted by twitterfire
Internet & Networking "Google's efforts to improve Internet efficiency through the development of the SPDY (pronounced 'speedy') protocol got a major boost today when the chairman of the HTTP Working Group (HTTPbis), Mark Nottingham, called for it to be included in the HTTP 2.0 standard. SPDY is a protocol that's already used to a certain degree online; formal incorporation into the next-generation standard would improve its chances of being generally adopted."
Permalink for comment 504718
To read all comments associated with this story, please click here.
RE: no binary protocols please
by Alfman on Thu 26th Jan 2012 15:03 UTC in reply to "no binary protocols please"
Member since:


"The guys who initially developed this stuff had much much less powerful technology than we to today and they did just fine with text protocols."

I don't completely agree. Obviously ordinary users wouldn't care about a text protocol, so it's just techies. Text was very nice when we lacked tools to decode and analyze packets, but these days anyone with the need to view raw traffic shouldn't have trouble getting a hold of the tools to decode it. The most likely scenario is that the tool which captures the traffic would also transparently convert it to a readable format (ie wireshark & tcpdump). So even techies shouldn't care.

The big question is how much extra bandwidth and cpu overhead is consumed by using text protocols? The way HTTP is used today, I think the overhead is negligible compared to the large payloads. However, I can conceive of future scenarios where the HTTP overhead discourages the use of HTTP to manage traffic context.

Today's HTTP has issues with asynchronous/bidirectional communications, but assuming it gets fixed, there's alot of new potential applications for it. Consider future applications where the client can open simultaneous bidirectional data channels to the server in a single multiplexed HTTP pipe. Let's say it's a video conference/whiteboard/application sharing utility all running over one HTTP browser connection. The overhead of using a text protocol to manage the multiplexing should start to raise eyebrows.

Besides, I don't know of anyone who's complained that SSH's protocol isn't human readable (or even it's telnet precursor, who's handshake was also in binary).

Edit: Did anyone say anything about converting to a binary HTTP standard?

Edited 2012-01-26 15:10 UTC

Reply Parent Score: 2