On the no-UDP issue.. what's the implications then for someone like me using an ISP who sends UDP on land/sealine because of it's perceived 'timing' necessities yet sends http/tcpip usually via satellite
Audie, the implications are such:
UDP is a non-acknowledged protocol. It means the recipient is not going to acknowledge receiving the packet. This can result in lost packets since the packet will not be resent by the sender if the packet is lost in transit.
TCP on the other hand is an acknowledged protocol which means that if the recipient does not respond with an acknowledgement that it received the packet, it will be resent after a timeout period by the sender. Packets cannot be lost using TCP.
These are the only two protocols that are supported by a TCP/IP network. Think of UDP as regular snail mail and TCP as a registered letter. If hit packets were UDP, its very possible that actual hits never get recorded on the target. Since they are being sent via TCP, they will eventually be recorded...it just may take a couple of resends.
Regardless of whether you connect to the net through land lines, satellites, fiber, tin cans and string or whatever, a TCP/IP connection will support UDP and TCP.
-Ding