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/000480.html | |
download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-July/000480.html')
-rw-r--r-- | pipermail/nel/2001-July/000480.html | 92 |
1 files changed, 92 insertions, 0 deletions
diff --git a/pipermail/nel/2001-July/000480.html b/pipermail/nel/2001-July/000480.html new file mode 100644 index 00000000..f1190c50 --- /dev/null +++ b/pipermail/nel/2001-July/000480.html @@ -0,0 +1,92 @@ +<!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:cblt%40cblt.org"> + <LINK REL="Previous" HREF="000479.html"> + <LINK REL="Next" HREF="000484.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] TCP vs. UDP</H1> + <B>Nicolas Hognon</B> + <A HREF="mailto:cblt%40cblt.org" + TITLE="[Nel] TCP vs. UDP">cblt@cblt.org</A><BR> + <I>Thu, 05 Jul 2001 17:00:15 +0200</I> + <P><UL> + <LI> Previous message: <A HREF="000479.html">[Nel] TCP vs. UDP</A></li> + <LI> Next message: <A HREF="000484.html">[Nel] TCP vs. UDP</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#480">[ date ]</a> + <a href="thread.html#480">[ thread ]</a> + <a href="subject.html#480">[ subject ]</a> + <a href="author.html#480">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>><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> +You mean you are thinking about creating a tinny TCP over UDP. +If you want to do that i'm not sure it's a good idea. + +in "effective TCP/IP Programming" Jon C. Snader says +in +Tip 7 : Don't Underestimate The Performance of TCP +Tip 8 : Avoid Reinventing TCP + +Ok, i'm not very useful in this conversation but +i'm not (yet :)) a network guru .... + +I'm interest by answer from other people. + +><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? K- +</I>><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> + + +-- +Nicolas Hognon +<A HREF="mailto:nicolash@virtools.com">nicolash@virtools.com</A> + +Virtools - The Behavior Company +Tel. (+33) 1 42 71 46 86 / Fax. (+33) 1 42 71 86 53 +<A HREF="http://www.virtools.com/">http://www.virtools.com/</A> + + +</pre> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000479.html">[Nel] TCP vs. UDP</A></li> + <LI> Next message: <A HREF="000484.html">[Nel] TCP vs. UDP</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#480">[ date ]</a> + <a href="thread.html#480">[ thread ]</a> + <a href="subject.html#480">[ subject ]</a> + <a href="author.html#480">[ author ]</a> + </LI> + </UL> +</body></html> |