From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <CAEoi9W6z_48wm8Jx__Meodnr50g0Ba00wqyfVrv0SP=Xb5ZHcw@mail.gmail.com>
References: <CA+Tk8fzHcHvd-yMfwVXSC7hpH-AsA1ocYhe0m+K7mPar=HF-sA@mail.gmail.com>
	<CADSkJJVcsffzZo6En5A8DTApZULxkqCuzXEgKbFvv8eRjm2DpQ@mail.gmail.c>
	<011b9189eff1a19b0e074faf782dd598@coraid.com>
	<CAG3N4d9ROH_kOBCPSj1fPfk7NoJZqNKSRLxMYdD7PV5FD7-11w@mail.gmail.com>
	<CAEoi9W6z_48wm8Jx__Meodnr50g0Ba00wqyfVrv0SP=Xb5ZHcw@mail.gmail.com>
Date: Tue, 20 Mar 2012 22:30:53 +0200
Message-ID: <CA+Tk8fy5tdsGdd6GDfFpDXN40fZez_+C2ierQcHR6BZTmgPcsw@mail.gmail.com>
From: Ciprian Dorin Craciun <ciprian.craciun@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: 6c657fb0-ead7-11e9-9d60-3106f5b1d025

On Tue, Mar 20, 2012 at 14:32, Dan Cross <crossd@gmail.com> wrote:
> 9P itself is not a stream-oriented
> protocol, nor is it what one would generally call, 'transport
> technology.'


    I would beg to differ on this subject... Because a lot of tools in
the Plan9 environment expose their facilities as 9p file systems, but
expose other semantics than that of "generic" files -- i.e. a
contiguous stream of bytes from start to EOF -- like for example RPC
semantic in case of factotum; thus I would say that 9p is used as a
"session" layer in the OSI terminology. (But as in TCP/IP stack we
don't have other layers between "transport" and "application" I would
call it a "transport" layer in such a context.)