From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <011b9189eff1a19b0e074faf782dd598@coraid.com>
References: <CA+Tk8fzHcHvd-yMfwVXSC7hpH-AsA1ocYhe0m+K7mPar=HF-sA@mail.gmail.com>
	<CADSkJJVcsffzZo6En5A8DTApZULxkqCuzXEgKbFvv8eRjm2DpQ@mail.gmail.c>
	<011b9189eff1a19b0e074faf782dd598@coraid.com>
Date: Tue, 20 Mar 2012 13:42:39 +0200
Message-ID: <CAG3N4d9ROH_kOBCPSj1fPfk7NoJZqNKSRLxMYdD7PV5FD7-11w@mail.gmail.com>
From: Yaroslav <yarikos@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [9fans] Regarding 9p based "protocols" message framing
Topicbox-Message-UUID: 6c15ce8e-ead7-11e9-9d60-3106f5b1d025

>  Why was I puzzled: because as a non Plan9 user / developer, I
> usually think of the underlaying transport technology (be it sockets
> or 9p) as a stream of bytes without explicit framing.

As I understand, 9P itself is designed to operate on top of a
message-oriented transport; however, it has everything required to run
over a stream, esp. message length at beginning of every message.
Framing is done by the library: the read9pmsg routine performs as many
reads as necessary to return a complete 9P message to the caller.