From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <21717812-8eaa-40ed-b993-9c91287e8445@email.android.com> Date: Mon, 10 Aug 2015 16:40:53 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11c37be08b27f2051cf6cf6e Subject: Re: [9fans] read9pmsg usage Topicbox-Message-UUID: 65aa207a-ead9-11e9-9d60-3106f5b1d025 --001a11c37be08b27f2051cf6cf6e Content-Type: text/plain; charset=UTF-8 As a further historical note, originally 9P required a stream that preseved record boundaries, and the reliable datagram protocol IL/IP and pipes did that. Once TCP/IP was used, there was some fussing needed to work out where the records were, so the revision 9P2000 added a size and the stream didn't need to preserve boundaries itself. As an aside, John Day in his interesting Patterns in Network Architecture (http://goo.gl/4WKu1r) discusses whether protocols should preserve record boundaries, and concludes that they should (assuming I remember correctly!). --001a11c37be08b27f2051cf6cf6e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
As a further historical note, o= riginally 9P required a stream that preseved record boundaries, and the rel= iable datagram protocol IL/IP and pipes did that. Once TCP/IP was used, the= re was some fussing needed to work out where the records were, so the revis= ion 9P2000 added a size and the stream didn't need to preserve boundari= es itself. As an aside, John Day in his interesting Patterns in Network Arc= hitecture (http://goo.gl/4WKu1r) discu= sses whether protocols should preserve record boundaries, and concludes tha= t they should (assuming I remember correctly!).
--001a11c37be08b27f2051cf6cf6e--