re: http://www.garlic.com/~lynn/2014b.html#39 Resistance to Java http://www.garlic.com/~lynn/2014b.html#44 Resistance to Java http://www.garlic.com/~lynn/2014b.html#46 Resistance to Java
part of the issue SNA was pretty much dictated by VTAM/NCP ... which was a low-speed, dumb terminal communication paradigm. It was a herculean task to do anything approaching networking. it was one of the reasons I called HSDT (high-speed data transport) to differentiate from SNA http://www.garlic.com/~lynn/subnetwork.html#hsdt also, arpanet IMP networking (before 1jan1983 internetworking tcp/ip), sna, and OSI were pretty much all single administrative domain (no internetworking). note that it wasn't just sna that lost out to tcp/ip in the late 80s ... also in the late 80s the federal government had mandated the elimination of the internet and move over to GOSIP (aka OSI) which also didn't happen. old email mentioning NSFNET backbone (precusor to modern internet) http://www.garlic.com/~lynn/lhwemail.html#nsfnet NSFNET backbone related posts http://www.garlic.com/~lynn/subnetwork.html#nsfnet internet related posts http://www.garlic.com/~lynn/subnetwork.html#internet past article from MIT that the original purpose of NSFNET backbone was to hook together the NSF supercomputer centers ... sort of the foundation of GRID computing and modern cloud computing http://www.technologyreview.com/featuredstory/401444/grid-computing/ other trivia ... before he passed, the long time RFC (aka internet standards) Editor (Postel) use to let me do some of STD1 ... based on some of the stuff i do for RFC index http://www.garlic.com/~lynn/rfcietff.htm -- virtualization experience starting Jan1968, online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
