News for hackers. Stuff that matters.
Re:Google Modifies HTTP, Makes Chrome 50% Faster by xuhu on Monday April 11, 2011 @05:28AM (#2431998)
Unlike HTTP, SPDY is no longer plain-text (it uses a packet structure similar to TCP headers).

While Wireshark's usability has been constantly improving, I will miss being able to do:

  $ telnet google.com 80
  GET / HTTP/1.1
  Host: google.com
Re:Google Modifies HTTP, Makes Chrome 50% Faster by jrockway on Monday April 11, 2011 @05:40AM (#2432022)
This is a reasonable concern, but the reality is that:

  $ telnet google.com 80
  GET / HTTP/1.0
Is just going to become:

  >>> use SPDY;
  >>> SPDY->dump('http://www.google.com/);
Re:Google Modifies HTTP, Makes Chrome 50% Faster by 1337p337 on Monday April 11, 2011 @04:13PM (#2434175)
Plain-text formats have always been slower for things that are not plain text. But even 30 years ago, when computers were even slower, Unix designers decided plain text was still the way to go, because it was easier to debug and easier for humans to work with. No specialized tools required, no poring over hex dumps. HTML won over other document formats. JSON and XML won over other binary formats. Any coder can look at JSON and see what is being transferred, without the aid of anything but a text editor. Plain-text marshalling formats for binary data (e.g., base64) are still useful for pasting data into an email or adding ssh keys to authorized_keys with "cat >>".

This is perhaps a long way of saying that I don't expect that having tool support makes SPDY any nicer.

Re:Google Modifies HTTP, Makes Chrome 50% Faster by gcb on Monday April 11, 2011 @06:17AM (#2432086)
Less true for tcp dumps

which I believe was the previous poster intention since he mentioned wire shark..

Also piping bunch of unix command will suffer a little of they

Re:Google Modifies HTTP, Makes Chrome 50% Faster by mahmud on Monday April 11, 2011 @08:11AM (#2432278)
swig + libpcap should get you there for any mainstream language (assuming you're on a real OS.)
Re:Google Modifies HTTP, Makes Chrome 50% Faster by judofyr on Monday April 11, 2011 @06:43AM (#2432119)
SPDY is always encrypted, so it would be more fair to compare it with HTTPS, where you can't do anything like that anyway.
Re:Google Modifies HTTP, Makes Chrome 50% Faster by Toucan on Monday April 11, 2011 @09:21AM (#2432450)
Sure you can. openssl s_client -connect google.com:443

Not sure what the equivalent is on windows though.

Re:Google Modifies HTTP, Makes Chrome 50% Faster by judofyr on Monday April 11, 2011 @10:30AM (#2432664)
Sure, but that's not telnet. I would assume you could make a similar tool for debugging SPDY too.
Re:Google Modifies HTTP, Makes Chrome 50% Faster by bruce511 on Monday April 11, 2011 @10:15AM (#2432614)
not surprisingly it's... openssl s_client -connect google.com:443
Re:Google Modifies HTTP, Makes Chrome 50% Faster by tonfa on Monday April 11, 2011 @05:38AM (#2432016)
They probably won't switch off http support before a very long time :) So you won't miss anything.
Re:Google Modifies HTTP, Makes Chrome 50% Faster by tedjdziuba on Monday April 11, 2011 @10:16AM (#2432619)
Sigh. Those who abandon Unix principles deserve whatever they get.
Re:Google Modifies HTTP, Makes Chrome 50% Faster by SimHacker on Monday April 11, 2011 @11:15AM (#2432825)
Efficiency. You can keep your Unix principled autoconf scripts, thank you.