aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2001-March/000366.html
diff options
context:
space:
mode:
Diffstat (limited to 'pipermail/nel/2001-March/000366.html')
-rw-r--r--pipermail/nel/2001-March/000366.html113
1 files changed, 113 insertions, 0 deletions
diff --git a/pipermail/nel/2001-March/000366.html b/pipermail/nel/2001-March/000366.html
new file mode 100644
index 00000000..70a4362d
--- /dev/null
+++ b/pipermail/nel/2001-March/000366.html
@@ -0,0 +1,113 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Nel] newbies about packet schema</TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:jaleco%40svr1.gameone.com.tw">
+ <LINK REL="Previous" HREF="000365.html">
+ <LINK REL="Next" HREF="000367.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Nel] newbies about packet schema</H1>
+ <B>jaleco</B>
+ <A HREF="mailto:jaleco%40svr1.gameone.com.tw"
+ TITLE="[Nel] newbies about packet schema">jaleco@svr1.gameone.com.tw</A><BR>
+ <I>Thu, 8 Mar 2001 10:02:46 +0800</I>
+ <P><UL>
+ <LI> Previous message: <A HREF="000365.html">[Nel] 'data/' bug</A></li>
+ <LI> Next message: <A HREF="000367.html">[Nel] newbies about packet schema</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#366">[ date ]</a>
+ <a href="thread.html#366">[ thread ]</a>
+ <a href="subject.html#366">[ subject ]</a>
+ <a href="author.html#366">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>This is a multi-part message in MIME format.
+
+------=_NextPart_000_000A_01C0A7B6.ECAB2720
+Content-Type: text/plain;
+ charset=&quot;big5&quot;
+Content-Transfer-Encoding: quoted-printable
+
+&gt;<i>I am not familiar with the snowball protocol (&quot;packet schema&quot;).
+</I>&gt;<i>However, I assure you that the article is correct --- attempting
+</I>&gt;<i>to turn TCP from a byte stream into a sequenced message stream by
+</I>&gt;<i>disabling Nagle will not work. The only way to implement message
+</I>&gt;<i>semantics on top of TCP is to add your own packetization to the
+</I>&gt;<i>byte stream. For example,
+</I>
+thanks .
+but snowball seem have no any packet schema , just disable Nagle .
+snowball assume send 50 byte , it will receive 50 byte once.
+if send 50 byte , the recevie 25 byte twice,if it happen,snow ball is =
+die.
+does it will happen in real world ( send n byte, recive total n byte by =
+more than one recive ) ?
+
+
+
+
+------=_NextPart_000_000A_01C0A7B6.ECAB2720
+Content-Type: text/html;
+ charset=&quot;big5&quot;
+Content-Transfer-Encoding: quoted-printable
+
+&lt;!DOCTYPE HTML PUBLIC &quot;-//W3C//DTD HTML 4.0 Transitional//EN&quot;&gt;
+&lt;HTML&gt;&lt;HEAD&gt;
+&lt;META http-equiv=3DContent-Type content=3D&quot;text/html; charset=3Dbig5&quot;&gt;
+&lt;META content=3D&quot;MSHTML 5.50.4522.1800&quot; name=3DGENERATOR&gt;
+&lt;STYLE&gt;&lt;/STYLE&gt;
+&lt;/HEAD&gt;
+&lt;BODY bgColor=3D#ffffff&gt;
+&lt;DIV&gt;&lt;FONT size=3D2&gt;&lt;FONT size=3D3&gt;&amp;gt;I am not familiar with the =
+snowball protocol=20
+(&quot;packet schema&quot;).&lt;BR&gt;&amp;gt;However, I assure you that the article is =
+correct ---=20
+attempting&lt;BR&gt;&amp;gt;to turn TCP from a byte stream into a sequenced =
+message stream=20
+by&lt;BR&gt;&amp;gt;disabling Nagle will not work.&amp;nbsp; The only way to implement =
+
+message&lt;BR&gt;&amp;gt;semantics on top of TCP is to add your own packetization =
+to=20
+the&lt;BR&gt;&amp;gt;byte stream.&amp;nbsp; For example,&lt;/FONT&gt;&lt;/FONT&gt;&lt;/DIV&gt;
+&lt;DIV&gt;&lt;FONT size=3D2&gt;&lt;FONT size=3D3&gt;&lt;/FONT&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/DIV&gt;
+&lt;DIV&gt;&lt;FONT size=3D2&gt;&lt;FONT size=3D3&gt;thanks .&lt;/FONT&gt;&lt;/FONT&gt;&lt;/DIV&gt;
+&lt;DIV&gt;&lt;FONT size=3D2&gt;&lt;FONT size=3D3&gt;but snowball seem&amp;nbsp; have&amp;nbsp; no =
+any packet=20
+schema , just disable Nagle .&lt;/FONT&gt;&lt;/FONT&gt;&lt;/DIV&gt;
+&lt;DIV&gt;&lt;FONT size=3D2&gt;&lt;FONT size=3D3&gt;snowball assume send 50 byte , it =
+will receive 50=20
+byte once.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/DIV&gt;
+&lt;DIV&gt;&lt;FONT size=3D2&gt;&lt;FONT size=3D3&gt;if send 50 byte , the recevie 25 byte =
+twice,if it=20
+happen,snow ball is die.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/DIV&gt;
+&lt;DIV&gt;does it will happen in real world ( send n byte, recive total n =
+byte by=20
+more than one recive ) ?&lt;/DIV&gt;
+&lt;DIV&gt;&lt;FONT size=3D2&gt;&lt;FONT size=3D3&gt;&lt;/FONT&gt;&amp;nbsp;&lt;/DIV&gt;
+&lt;DIV&gt;&lt;BR&gt;&lt;/DIV&gt;&lt;/FONT&gt;&lt;/BODY&gt;&lt;/HTML&gt;
+
+------=_NextPart_000_000A_01C0A7B6.ECAB2720--
+
+
+
+</pre>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI> Previous message: <A HREF="000365.html">[Nel] 'data/' bug</A></li>
+ <LI> Next message: <A HREF="000367.html">[Nel] newbies about packet schema</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#366">[ date ]</a>
+ <a href="thread.html#366">[ thread ]</a>
+ <a href="subject.html#366">[ subject ]</a>
+ <a href="author.html#366">[ author ]</a>
+ </LI>
+ </UL>
+</body></html>