News for hackers. Stuff that matters.
Re:SPDY of the Future Might Blow Your Mind Today by jcrites on Thursday January 05, 2012 @10:27PM (#3431814)
> Requiring machine-to-machine communication to do heavy parsing is a bad idea.

Why? Machine-to-machine communication is for machines, after all, isn't it?

What you call "heavy parsing" is heavy parsing for humans. It's actually easier for machines, because they simply reference (and verify) an offset.

Are you advocating designing a protocol primarily around how easy it is to interactively troubleshoot? Certainly that has value, but on the modern Internet, is it really the dominating concern?

Re:SPDY of the Future Might Blow Your Mind Today by zobzu on Thursday January 05, 2012 @10:54PM (#3431882)
To the point:

- try checking what a webapp does. TRIVIAL. We're talking minutes.

- try checking what a binary app on your computer does. one with DRMs or advanced "anti crack" stuff for example. FREAKING HARD. Even if you're a wizard, it still takes a few hours. For mortals, we're talking weeks. Weeks!

And that my friend, is why what you wrote is wrong.

Re:SPDY of the Future Might Blow Your Mind Today by resnamen on Friday January 06, 2012 @01:18AM (#3432247)
Definitely not the case with HTTPS, which looks like binary garbage over the wire but whose payload is quite transparent once decoded by SSL.
Re:SPDY of the Future Might Blow Your Mind Today by drivebyacct2 on Friday January 06, 2012 @12:28AM (#3432108)
How are you "checking what a webapp does"?

You're using the browser or WireShark almost guaranteedly. You can continue to use the same methods with SPDY or compressed/proxied SPDY.