3 ms·

In an engineering context, it's necessary to be specific. Otherwise, someone unfamiliar with the terms being used might come away with the wrong idea. IPX is v

In an engineering context, it's necessary to be specific. Otherwise, someone unfamiliar with the terms being used might come away with the wrong idea. IPX is virtually dead, but it would be entirely possible to do HTTP over IPX if you had a web server and client that could bind to an IPX interface.

nitrogen 13y ago
I'll be sure to specify a specific protocol over TCP over IPv4/IPv6 over any suitable layer 2 interface if I'm ever specifying such a system for implementation. On HN, I would hope that anyone confused by the terms knows they can look them up on Wikipedia: https://en.wikipedia.org/wiki/HTTP https://en.wikipedia.org/wiki/HTTP https://en.wikipedia.org/wiki/Transmission_Control_Protocol https://en.wikipedia.org/wiki/Transmission_Control_Protocol https://en.wikipedia.org/wiki/IPX https://en.wikipedia.org/wiki/IPX https://en.wikipedia.org/wiki/Internet_protocol_suite https://en.wikipedia.org/wiki/Internet_protocol_suite
- bradleyland 13y ago
  Sorry, I didn't mean to come across as being pedantic :) I really do think the distinction is important. It's a foundational element of the language that ties software and hardware together. It's the reason we have things like the OSI model. A couple of years ago I had a temporary run in telecom, working with a company on a nation wide VoIP roll out. This was the first project where I was working on technologies that were completely outside the realm of your typical web application. I was surprised to find so many similarities. SIP, for example, looks a lot like HTTP. The distinction between messaging and media gave me new insights in to web programming. As I learned more and more about telephony, it became obvious that the common language between web and telecom technologies was the separation of layers in the various protocols that make up each stack. Knowing, and respecting, the language that is used to communicate these concepts helped me transition quickly between technologies. Because of that, I try to make an effort to share this knowledge with others. My intent is to inspire, not to chastise :) I didn't do a very good job of that in my original comment.

nitrogen 13y ago

I'll be sure to specify a specific protocol over TCP over IPv4/IPv6 over any suitable layer 2 interface if I'm ever specifying such a system for implementation. On HN, I would hope that anyone confused by the terms knows they can look them up on Wikipedia: https://en.wikipedia.org/wiki/HTTP https://en.wikipedia.org/wiki/HTTP https://en.wikipedia.org/wiki/Transmission_Control_Protocol https://en.wikipedia.org/wiki/Transmission_Control_Protocol https://en.wikipedia.org/wiki/IPX https://en.wikipedia.org/wiki/IPX https://en.wikipedia.org/wiki/Internet_protocol_suite https://en.wikipedia.org/wiki/Internet_protocol_suite

bradleyland 13y ago
Sorry, I didn't mean to come across as being pedantic :) I really do think the distinction is important. It's a foundational element of the language that ties software and hardware together. It's the reason we have things like the OSI model. A couple of years ago I had a temporary run in telecom, working with a company on a nation wide VoIP roll out. This was the first project where I was working on technologies that were completely outside the realm of your typical web application. I was surprised to find so many similarities. SIP, for example, looks a lot like HTTP. The distinction between messaging and media gave me new insights in to web programming. As I learned more and more about telephony, it became obvious that the common language between web and telecom technologies was the separation of layers in the various protocols that make up each stack. Knowing, and respecting, the language that is used to communicate these concepts helped me transition quickly between technologies. Because of that, I try to make an effort to share this knowledge with others. My intent is to inspire, not to chastise :) I didn't do a very good job of that in my original comment.