Well, what are the cases where a UDP transmission would fail, but a TCP connection would succeed?
Packet loss, and it would make both protocols fail. TCP is resilient to some amount but it would get affected by increased delays due to timeouts and retransmissions.
Normally UDP has always priority over TCP traffic, so on congestions you can expect UDP traffic go thru and TCP traffic get delayed (or dropped if buffers go full) until congestion stops.
Its not a firewall, as we'd already be on a port that a firewall would probably block.
Also note that on older Windows versions, it is difficult to determine error responses on application level to UDP packets which are sent by ICMP messages (though most firewalls just drop packets and don't return proper error). They do not get exposed to applications by default. 2000 and XP make it hassle free. Following url has the details, but I wonder if Java allows using the workarounds..
http://www.sockets.com/ws2_stat.htm#TCPIP
How well can we disguise the fact that we're a freenet node over UDP?
It is easier to capture and monitor TCP traffic if the communications between nodes is limited by connection boundaries (eg. definite connection setup and teardown on application level). UDP makes using such assumption harder as there is no definite connection boundary, only packet boundary.
_______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
