From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Fri, 16 Mar 2012 13:49:07 -0400
To: 9fans@9fans.net
Message-ID: <011b9189eff1a19b0e074faf782dd598@coraid.com>
In-Reply-To: <CADSkJJVcsffzZo6En5A8DTApZULxkqCuzXEgKbFvv8eRjm2DpQ@mail.gmail.c>
References: <CA+Tk8fzHcHvd-yMfwVXSC7hpH-AsA1ocYhe0m+K7mPar=HF-sA@mail.gmail.com>
	<CADSkJJVcsffzZo6En5A8DTApZULxkqCuzXEgKbFvv8eRjm2DpQ@mail.gmail.c>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Regarding 9p based "protocols" message framing
Topicbox-Message-UUID: 6a2b4b6c-ead7-11e9-9d60-3106f5b1d025

On Fri Mar 16 13:37:36 EDT 2012, rsc@swtch.com wrote:
> On Fri, Mar 16, 2012 at 7:40 AM, Ciprian Dorin Craciun
> <ciprian.craciun@gmail.com> wrote:
> > =C2=A0Why 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.
>=20
> Even outside Plan 9, this is not always the case.
> UDP, IP, ethernet, Unix datagram sockets, email, HTTP.
> They're all message-based protocols.

of course inside plan 9, pipes are repect write boundaries, too.

- erik