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/000488.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to '')
| -rw-r--r-- | pipermail/nel/2001-July/000488.html | 97 |
1 files changed, 97 insertions, 0 deletions
diff --git a/pipermail/nel/2001-July/000488.html b/pipermail/nel/2001-July/000488.html new file mode 100644 index 00000000..e59240d6 --- /dev/null +++ b/pipermail/nel/2001-July/000488.html @@ -0,0 +1,97 @@ +<!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:David.Mentre%40inria.fr"> + <LINK REL="Previous" HREF="000490.html"> + <LINK REL="Next" HREF="000501.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] TCP vs. UDP</H1> + <B>David Mentre</B> + <A HREF="mailto:David.Mentre%40inria.fr" + TITLE="[Nel] TCP vs. UDP">David.Mentre@inria.fr</A><BR> + <I>06 Jul 2001 09:54:59 +0200</I> + <P><UL> + <LI> Previous message: <A HREF="000490.html">[Nel] TCP vs. UDP</A></li> + <LI> Next message: <A HREF="000501.html">[Nel] TCP vs. UDP</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#488">[ date ]</a> + <a href="thread.html#488">[ thread ]</a> + <a href="subject.html#488">[ subject ]</a> + <a href="author.html#488">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, + +><i>From all other posters, it seems that performance result is highly +</I>dependent on implementation. So to make the Really Good Choice(tm), you +should have both and choose according to *figures*. So I would do that +in the following order : + + 1. design a "packet sending" layer which allows messages + sending/receiving with semantics in mind (see Vincent's post in the + same thread). Maybe NeL has already that, I haven't check the + source, sorry. + + 2. implement this layer using TCP. Should be straightforward. + + => gives you a backup implementation + + => gives you basic performance figures + + 3. design and implement UDP implementation_s_ with various + requirements depending on the following parameters: + + - packet loss or not + + - in order delivery or not + + You could start from the easiest (packet loss && out of order <=> + raw UDP) and incrementally develop more complicated ones. + + 4. substitute parts of TCP implementation (chat, position packets, ...) + with the corresponding UDP based protocol + + 5. implement a benchmark and test, test, test, ... ; then go to step 4 + and loop + + +Ok. I don't propose any line of code so you could directly throw this +post to /dev/null but you asked for comments. ;) + +BTW, what is your Linux configuration? I've been stuck with the need to +reinstall everything (X, STLport, freetype) on my debian machine. So it +may be easier to install the Linux distribution your are using at Nevrax +on some spare partition to try to "enter the loop". + +Best regards, +d. +-- + <A HREF="mailto:David.Mentre@inria.fr">David.Mentre@inria.fr</A> + Opinions expressed here are only mine. + +</pre> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000490.html">[Nel] TCP vs. UDP</A></li> + <LI> Next message: <A HREF="000501.html">[Nel] TCP vs. UDP</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#488">[ date ]</a> + <a href="thread.html#488">[ thread ]</a> + <a href="subject.html#488">[ subject ]</a> + <a href="author.html#488">[ author ]</a> + </LI> + </UL> +</body></html> |