diff options
author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
---|---|---|
committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-July/000489.html | |
download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-July/000489.html')
-rw-r--r-- | pipermail/nel/2001-July/000489.html | 130 |
1 files changed, 130 insertions, 0 deletions
diff --git a/pipermail/nel/2001-July/000489.html b/pipermail/nel/2001-July/000489.html new file mode 100644 index 00000000..5d04e7f9 --- /dev/null +++ b/pipermail/nel/2001-July/000489.html @@ -0,0 +1,130 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] TCP vs. UDP</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:alfred%40mazuma.net.au"> + <LINK REL="Previous" HREF="000506.html"> + <LINK REL="Next" HREF="000492.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] TCP vs. UDP</H1> + <B>alfred</B> + <A HREF="mailto:alfred%40mazuma.net.au" + TITLE="[Nel] TCP vs. UDP">alfred@mazuma.net.au</A><BR> + <I>Fri, 6 Jul 2001 19:41:50 +1000</I> + <P><UL> + <LI> Previous message: <A HREF="000506.html">[Nel] Linux compiling (was: TCP vs. UDP)</A></li> + <LI> Next message: <A HREF="000492.html">[Nel] TCP vs. UDP</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#489">[ date ]</a> + <a href="thread.html#489">[ thread ]</a> + <a href="subject.html#489">[ subject ]</a> + <a href="author.html#489">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>You *must* replace your transport mechanism with UDP :) + +TCP provides (nah, ensures) reliable delivery of data, but it can spend a +long time transmitting (especially on clogged up links). Between packet +errors and backoffs due to packet drops it can easily take 2seconds plus to +get data down the "tcp pipe". And seeing its a pipe, everything behind it is +"backed" up. So, time critical data can't just jump past useless data (like +MOTD's,etc). + +With UDP on the otherhand, you lose the reliable data, but you get your +timeliness. Because of the datagram nature of transmission, you can also +implement independant "streams", with reliablity on some streams (via extra +software layers) and timeliness on others (auto drop of old data for eg). + +Btw, you cannot "design your own layer", because you need to use the +existing internet to send your data (which will only accept UDP and TCP). +However, they probably did add to UDP, by adding an extra software layer to +provide "reliable udp" (its almost trivial to do). + +Any, UDP is the only option that is sensible for anything that has time +critical performance or for things with mutliple "data channels". + +BTW, I do stuff like this for a living (I am a network researched for +www.dsto.defence.gov.au), with a fair bit of work in the voice arena, so I +have some experience backing me up here :) + + +----- Original Message ----- +From: "Vianney Lecroart" <<A HREF="mailto:lecroart@nevrax.com">lecroart@nevrax.com</A>> +To: <<A HREF="mailto:nel@nevrax.org">nel@nevrax.org</A>> +Sent: Friday, July 06, 2001 12:36 AM +Subject: [Nel] TCP vs. UDP + + +><i> Hi everybody! +</I>><i> +</I>><i> Let's talk a little bit about this great subject: TCP vs. UDP +</I>><i> +</I>><i> Thanks to Valerio Santinelli and Olivier Lejade, there's some cool +</I>><i> discussion about this subject on the web and I would like to have your +</I>><i> thought and discuss about this. +</I>><i> +</I>><i> On Anarchy Online game, they only use TCP protocol between client and +</I>server +><i> (other commercial online game use UDP) and it seems that it causes lot of +</I>><i> problem like horrible ping or connection lost: +</I>><i> <A HREF="http://aoforums.funcom.com/showthread.php?threadid=26297">http://aoforums.funcom.com/showthread.php?threadid=26297</A> +</I>><i> +</I>><i> There's also a mail on the MUD-Dev mailing list talking about these +</I>problems +><i> here: +</I>><i> <A HREF="https://www.kanga.nu/archives/MUD-Dev-L/2001Q3/msg00009.php">https://www.kanga.nu/archives/MUD-Dev-L/2001Q3/msg00009.php</A> +</I>><i> +</I>><i> As you perhaps know, we only use TCP/IP (for server-server communication, +</I>><i> but also for the client-server connection) and we currently think more and +</I>><i> more about replacing the TCP client-server connection with a UDP one. +</I>><i> +</I>><i> In a first step, we would like to know your opinion about this choice. And +</I>><i> in a next step, we'll do some test about ping/packet lost and so on to +</I>><i> compare TCP and UDP, and we'll need your help to do that. +</I>><i> +</I>><i> Vianney Lecroart +</I>><i> --- +</I>><i> lead network programmer / nevrax.com +</I>><i> icq#: 6870415 +</I>><i> homepage: <A HREF="http://ace.planet-d.net">http://ace.planet-d.net</A> +</I>><i> www.geekcode.com: GCS/E d- s+++: a-- C+++$ UL++ P- L+++>+$ E+>- W++ N+ o? +</I>K- +><i> w++$ O- M- V- PS- PE? Y PGP t 5? X+ R- tv++ b- DI D+ G e++ h+ r-- y? +</I>><i> +</I>><i> +</I>><i> _______________________________________________ +</I>><i> Nel mailing list +</I>><i> <A HREF="mailto:Nel@nevrax.org">Nel@nevrax.org</A> +</I>><i> <A HREF="http://www.nevrax.org/mailman/listinfo.cgi/nel">http://www.nevrax.org/mailman/listinfo.cgi/nel</A> +</I>><i> +</I> + +</pre> + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000506.html">[Nel] Linux compiling (was: TCP vs. UDP)</A></li> + <LI> Next message: <A HREF="000492.html">[Nel] TCP vs. UDP</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#489">[ date ]</a> + <a href="thread.html#489">[ thread ]</a> + <a href="subject.html#489">[ subject ]</a> + <a href="author.html#489">[ author ]</a> + </LI> + </UL> +</body></html> |