From RFC 2616: HTTP communication usually takes place over TCP/IP connections. The default port is TCP 80, but other ports can be used. This does not preclude HTTP from being implemented on top of any other protocol on the Internet, or on other networks. HTTP only presumes a reliable transport; any protocol that provides such … Read more
Yes, you can use the same port number for both TCP and UDP. Many protocols already do this, for example DNS works on udp/53 and tcp/53. Technically the port pools for each protocol are completely independent, but for higher level protocols that can use either TCP or UDP it’s convention that they default to the … Read more
If you are using bash, you might as well write echo -n “hello” >/dev/udp/localhost/8000 and avoid all the idiosyncrasies and incompatibilities of netcat. This also works sending to other hosts, ex: echo -n “hello” >/dev/udp/remotehost/8000 These are not “real” devices on the file system, but bash “special” aliases. There is additional information in the Bash … Read more
Use the -p flag and add /udp suffix to the port number. -p 53160:53160/udp Full command sudo docker run -p 53160:53160 \ -p 53160:53160/udp -p 58846:58846 \ -p 8112:8112 -t -i aostanin/deluge /start.sh If you’re running boot2docker on Mac, be sure to forward the same ports on boot2docker to your local machine. You can also … Read more
TCP is a connection oriented stream over an IP network. It guarantees that all sent packets will reach the destination in the correct order. This imply the use of acknowledgement packets sent back to the sender, and automatic retransmission, causing additional delays and a general less efficient transmission than UDP. UDP is a connection-less protocol. … Read more
The most fundamental thing here probably is that you don’t want to transmit static images but only changes to the images, which essentially is analogous to video stream. My best guess is some very efficient (and heavily specialized and optimized) motion compensation algorithm, because most of the actual change in generic desktop usage is linear … Read more
They work almost the same as today. However, be sure you include [] around your IP. For example : http://[1fff:0:a88:85a3::ac1f]:8001/index.html Wikipedia has a pretty good article about IPv6: http://en.wikipedia.org/wiki/IPv6#Addressing
People say that the major thing TCP gives you is reliability. But that’s not really true. The most important thing TCP gives you is congestion control: you can run 100 TCP connections across a DSL link all going at max speed, and all 100 connections will be productive, because they all “sense” the available bandwidth. … Read more
It is true that a typical IPv4 header is 20 bytes, and the UDP header is 8 bytes. However it is possible to include IP options which can increase the size of the IP header to as much as 60 bytes. In addition, sometimes it is necessary for intermediate nodes to encapsulate datagrams inside of … Read more
This is one of my favorite questions. UDP is so misunderstood. In situations where you really want to get a simple answer to another server quickly, UDP works best. In general, you want the answer to be in one response packet, and you are prepared to implement your own protocol for reliability or to resend. … Read more