From: Ciprian Dorin Craciun <ciprian.craciun@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Regarding 9p based "protocols" message framing
Date: Tue, 20 Mar 2012 22:30:53 +0200 [thread overview]
Message-ID: <CA+Tk8fy5tdsGdd6GDfFpDXN40fZez_+C2ierQcHR6BZTmgPcsw@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W6z_48wm8Jx__Meodnr50g0Ba00wqyfVrv0SP=Xb5ZHcw@mail.gmail.com>
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.)
next prev parent reply other threads:[~2012-03-20 20:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 11:40 Ciprian Dorin Craciun
2012-03-16 17:04 ` Richard Miller
2012-03-16 17:36 ` Russ Cox
2012-03-16 17:55 ` Ciprian Dorin Craciun
[not found] ` <CADSkJJVcsffzZo6En5A8DTApZULxkqCuzXEgKbFvv8eRjm2DpQ@mail.gmail.c>
2012-03-16 17:49 ` erik quanstrom
2012-03-20 11:42 ` Yaroslav
2012-03-20 12:32 ` Dan Cross
2012-03-20 20:30 ` Ciprian Dorin Craciun [this message]
2012-03-21 1:22 ` Dan Cross
[not found] ` <CAEoi9W6t2WRPTYU6+JHfAZoRAe6aWxkuCDkXb1G+VAkZZ1kYug@mail.gmail.c>
2012-03-21 1:52 ` erik quanstrom
[not found] ` <CAEoi9W6z_48wm8Jx__Meodnr50g0Ba00wqyfVrv0SP=Xb5ZHcw@mail.gmail.c>
2012-03-20 15:57 ` erik quanstrom
2012-03-21 20:11 ` Yaroslav
2012-03-21 20:32 ` Anthony Sorace
2012-03-21 20:37 ` erik quanstrom
[not found] ` <CAG3N4d_Qd-dH4pZWXGdqoNTguSjGge1oLahTwJAk5nVLvzXvjQ@mail.gmail.c>
2012-03-21 20:27 ` erik quanstrom
2012-03-21 20:38 ` Anthony Sorace
2012-03-21 20:53 ` erik quanstrom
2012-03-21 21:24 ` cinap_lenrek
2012-03-21 21:27 ` erik quanstrom
2012-03-21 21:35 ` cinap_lenrek
2012-03-21 21:07 ` cinap_lenrek
2012-03-21 21:22 ` erik quanstrom
2012-03-21 21:16 ` David du Colombier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+Tk8fy5tdsGdd6GDfFpDXN40fZez_+C2ierQcHR6BZTmgPcsw@mail.gmail.com \
--to=ciprian.craciun@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).