3 ms·
The author has had some great experiences. I was struck by this post a few down from the Sun one: >"Sometime in late '80 I moved over to Amdahl's architecture
by bogomipz 4y ago
The author has had some great experiences. I was struck by this post a few down from the Sun one:
>"Sometime in late '80 I moved over to Amdahl's architecture group to work on data communications - X.25, SNA, etc. But that work wasn't too satisfying."
I believe X.25 would have been pretty cutting edge in 1980. A bit of trivia regarding this protocol AOL's network was built on X.25 and many ATM machines still use X.25. If you look in the back of any of those standalone crappy offbrand ATM machines you will see they are connected to an RJ 11 phone jack. Minitel in France also used it X.25 as well. It's almost hard to get your head around packet switched networks today with our ubiquitous Ethernet. If your curious:
https://www.historyofdomains.com/x25/ https://www.historyofdomains.com/x25/
- dan-robertson 4y agoThere are a few things leftover from those networking protocols that are still common: - X.509 for certificates - parts of LDAP - the 7 layer networking model, which at least made sense with the protocols it was modelling before it was jammed into tcp/ip networking. I think we should be thankful the list is relatively short.
- bogomipz 4y agoForward Error Correction and ASN.1 as well. I think it's kind of impressive though that those things survive more than 40 year later.
- Taniwha 4y agoThat whole network stack was based on a simple premise from the telco world ... that you should charge by the byte for a virtual end-to-end connection (just like we used to charge for a phone call - N bytes and M bytes/min). IP sort of busted that whole idea - the idea that you could (should!) just drop packets when things get tough ran against this whole idea - but it made TCP/IP easier to implement, and perform better, and most importantly move faster and be adopted as the standard we use today
- deleted 4y ago[deleted]