I am root. If you see me laughing, you‘d better have a backup!
Registered Member #1489
Joined: Sat Nov 11 2006 Location: Münster (Westphalia), Germany Posts: 1216
The internet was actualy invented by the US Department of Defense as a means of stable communication in case of an nuclear strike taking out one or more communication hubs. The rest of the hubs were still able to communicate with each other and relay the information to its destination. There is still a group of network protocols known as the DoD protocols, i. e. TCP/IP being two of them.
The World Wide Web, the visible part of the internet, was developed by academics at the CERN, an European science institution, as a means to share and publish information quickly and to everyone, thus fostering the academic discourse and speed up new insights and developments, which were not present with the paper way, which was slow and not reaching everyone who could contribute. They made the internet readable by the layman and that did jumpstart the global network.
@Tiger The first link is down. The second link is discussing the difference (advantages) of UDP and TCP/IP protocols. It's a good read.
What I think the author is suggesting is that UDP (kind of like "fire and forget") allows for packets to take alternate paths from one router (hop) to the other in hopes that it avoids congestion and arrives at the destination IP. Because of this it is the ideal protocol for serving as a host. Problem here is no guarantee of service (that packets will arrive at all).
With TCP/IP, you bind sockets prior to data being sent. Once a connection between destination IP and sender is made, packets will flow. Problem here, as the author mentions, is when there's "spikes" in transmissions (no buffer implementation) or no available bandwidth the packets will stall.
I can read up on how we're connecting (client to server, what protocol is being used, fixes, known issues, etc ...) but I doubt it's anything we can do on our end.
@ Cardinal we read up on ARPANET in our Network and Networkings class - good history there on how we were going to communicate in case the Russkies ever decided to hurl nukes our way. Did you ever read up on the ALOHAnet (http://en.wikipedia.org/wiki/ALOHAnet) ? Another good read on how wireless networking came about.
I am root. If you see me laughing, you‘d better have a backup!
Registered Member #1489
Joined: Sat Nov 11 2006 Location: Münster (Westphalia), Germany Posts: 1216
Naaah, reading up on Informix Databases, Windows Server and VMWare View Destkop Virtualization, with a little Exchange 2010 on the side, at the moment, plus a little learning on the side for MOS and MCITP certificates when I am not working. What You read above was info I read ages ago! (Those were the happy days, with more time to read and game!)
Joined: Mon Mar 29 2004 Location: Georgia, USA Posts: 1700
Typical comcast- tech visited and nothing fixed. Another visit scheduled for Wednesday when he can call those who know and hopefully get something resolved. Still, it looks as though the ip timeout is somewhere between Comcast's servers and my house, presumably on their line somewhere...