News for hackers. Stuff that matters.
Re:Designing Network Protocols by tptacek on Thursday February 23, 2012 @12:23AM (#3623916)
Not particularly fair. You also had XDR (ubiquitous on Unix systems), IIOP, TLV, ICE... not to mention what ever protocol designer for the past 20 years has used: network byte order integers and ASCII/UTF8 strings.

Some people just like ASCII, human readable protocols. There's nothing wrong with that, but it's a little silly to suggest that the options for a packed binary encoding in 2007 were limited because Thrift and Protocol Buffers were too new.

Re:Designing Network Protocols by jacques_chester on Thursday February 23, 2012 @12:26AM (#3623930)
You're right, to my shame. I should've thought of XDR myself, after suffering through a lecture on it at uni.

I'd be interested in the original designer's remarks on using existing wire serialisation formats.

Re:Designing Network Protocols by pquerna on Thursday February 23, 2012 @02:56AM (#3624190)
I mentioned ASN.1 DER, but I honestly didn't think I should go into a history of XDR or other encodings. I guess I can't skip any history in a blog post....
Re:Designing Network Protocols by tptacek on Thursday February 23, 2012 @01:06PM (#3625970)
I was responding to a comment, not your post. I don't think you really need to justify using an ASCII protocol (though, again, I think HTTP query arguments are a poor choice).