From: Dan Cross <crossd@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 08:32:02 -0400 [thread overview]
Message-ID: <CAEoi9W6z_48wm8Jx__Meodnr50g0Ba00wqyfVrv0SP=Xb5ZHcw@mail.gmail.com> (raw)
In-Reply-To: <CAG3N4d9ROH_kOBCPSj1fPfk7NoJZqNKSRLxMYdD7PV5FD7-11w@mail.gmail.com>
On Tue, Mar 20, 2012 at 7:42 AM, Yaroslav <yarikos@gmail.com> wrote:
>> 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.
Perhaps initially: over an IP network, 9P used to run over IL. With
9P2000, IL was deprecated and 9P was most typically run over TCP.
There was a very old message to 9fans (like, early 90's kind of old)
that implied that IL was much more efficient than TCP on the wire, but
it probably doesn't matter now. 9P itself is not a stream-oriented
protocol, nor is it what one would generally call, 'transport
technology.'
- Dan C.
next prev parent reply other threads:[~2012-03-20 12:32 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 [this message]
2012-03-20 20:30 ` Ciprian Dorin Craciun
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='CAEoi9W6z_48wm8Jx__Meodnr50g0Ba00wqyfVrv0SP=Xb5ZHcw@mail.gmail.com' \
--to=crossd@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).