aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2001-July/000488.html
blob: e59240d6e5c4765c4e8443bfedc109979811ff51 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
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,

&gt;<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 &quot;packet sending&quot; 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.

   =&gt; gives you a backup implementation

   =&gt; 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 &amp;&amp; out of order &lt;=&gt;
    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 &quot;enter the loop&quot;.

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>