Re: Fw: [discuss] Announcing: TCP NAT Traversal/Hole-Punching Library

--===============2049673968==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-9Sunt4QYT+luuhbmY6pM"


--=-9Sunt4QYT+luuhbmY6pM
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2005-09-28 at 20:45 +0200, Philippe Verdy wrote:
> Actually LimeWire does not need it, as it already has this feature since
> long, but now prefers UDP NAT traversal, which works even more often than
> TCP NET traversal.

UDP NAT traversal has been around since '97; this library makes it
possible for TCP. Operating system TCP stacks have, over the years, been
finely tuned for performance and congestion avoidance that make it
better suited for reliable transport than UDP. Many routers near the
edges of the Internet give UDP a lower priority and use RED to control
TCP streams to increase their performance and decrease packet-drops. TCP
encapsulate in UDP or some other reliable protocol encapsulated in UDP
cannot take advantage of router optimizations. Use of TCP is encouraged
for file-transfer applications, when possible, and our library serves to
make it possible more often. However, ultimately it is up to the
developers to choose between TCP and UDP.

cheers,
--=20
Saikat

--=-9Sunt4QYT+luuhbmY6pM
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDOwdinFltqi691/oRAmD3AJ9NNgHSpAECm4YpEdwVhw2mZtaYrgCfeRh4
PNWc9hfj+Wxl42XCjMMgo7E=
=kxfC
-----END PGP SIGNATURE-----

--=-9Sunt4QYT+luuhbmY6pM--


--===============2049673968==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
discuss mailing list
[email protected]
http://www.limewire.org/mailman/listinfo/discuss

--===============2049673968==--