From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <CA+Tk8fzHcHvd-yMfwVXSC7hpH-AsA1ocYhe0m+K7mPar=HF-sA@mail.gmail.com>
References: <CA+Tk8fzHcHvd-yMfwVXSC7hpH-AsA1ocYhe0m+K7mPar=HF-sA@mail.gmail.com>
Date: Fri, 16 Mar 2012 13:36:06 -0400
Message-ID: <CADSkJJVcsffzZo6En5A8DTApZULxkqCuzXEgKbFvv8eRjm2DpQ@mail.gmail.com>
Subject: Re: [9fans] Regarding 9p based "protocols" message framing
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 6a102508-ead7-11e9-9d60-3106f5b1d025

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.

Even outside Plan 9, this is not always the case.
UDP, IP, ethernet, Unix datagram sockets, email, HTTP.
They're all message-based protocols.

Russ