From 0ea5fc66924303d1bf73ba283a383e2aadee02f2 Mon Sep 17 00:00:00 2001 From: neodarz Date: Sat, 11 Aug 2018 20:21:34 +0200 Subject: Initial commit --- pipermail/nel/2001-March/000366.html | 113 +++++++++++++++++++++++++++++++++++ 1 file changed, 113 insertions(+) create mode 100644 pipermail/nel/2001-March/000366.html (limited to 'pipermail/nel/2001-March/000366.html') 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 @@ + + + + [Nel] newbies about packet schema + + + + + + +

[Nel] newbies about packet schema

+ jaleco + jaleco@svr1.gameone.com.tw
+ Thu, 8 Mar 2001 10:02:46 +0800 +

+
+ +
This is a multi-part message in MIME format.
+
+------=_NextPart_000_000A_01C0A7B6.ECAB2720
+Content-Type: text/plain;
+	charset="big5"
+Content-Transfer-Encoding: quoted-printable
+
+>I am not familiar with the snowball protocol ("packet schema").
+>However, I assure you that the article is correct --- attempting
+>to turn TCP from a byte stream into a sequenced message stream by
+>disabling Nagle will not work.  The only way to implement message
+>semantics on top of TCP is to add your own packetization to the
+>byte stream.  For example,
+
+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="big5"
+Content-Transfer-Encoding: quoted-printable
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML><HEAD>
+<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dbig5">
+<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
+<STYLE></STYLE>
+</HEAD>
+<BODY bgColor=3D#ffffff>
+<DIV><FONT size=3D2><FONT size=3D3>&gt;I am not familiar with the =
+snowball protocol=20
+("packet schema").<BR>&gt;However, I assure you that the article is =
+correct ---=20
+attempting<BR>&gt;to turn TCP from a byte stream into a sequenced =
+message stream=20
+by<BR>&gt;disabling Nagle will not work.&nbsp; The only way to implement =
+
+message<BR>&gt;semantics on top of TCP is to add your own packetization =
+to=20
+the<BR>&gt;byte stream.&nbsp; For example,</FONT></FONT></DIV>
+<DIV><FONT size=3D2><FONT size=3D3></FONT></FONT>&nbsp;</DIV>
+<DIV><FONT size=3D2><FONT size=3D3>thanks .</FONT></FONT></DIV>
+<DIV><FONT size=3D2><FONT size=3D3>but snowball seem&nbsp; have&nbsp; no =
+any packet=20
+schema , just disable Nagle .</FONT></FONT></DIV>
+<DIV><FONT size=3D2><FONT size=3D3>snowball assume send 50 byte , it =
+will receive 50=20
+byte once.</FONT></FONT></DIV>
+<DIV><FONT size=3D2><FONT size=3D3>if send 50 byte , the recevie 25 byte =
+twice,if it=20
+happen,snow ball is die.</FONT></FONT></DIV>
+<DIV>does it will happen in real world ( send n byte, recive total n =
+byte by=20
+more than one recive ) ?</DIV>
+<DIV><FONT size=3D2><FONT size=3D3></FONT>&nbsp;</DIV>
+<DIV><BR></DIV></FONT></BODY></HTML>
+
+------=_NextPart_000_000A_01C0A7B6.ECAB2720--
+
+
+
+
+ + + +
+

+ -- cgit v1.2.1