9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9p2000 query
Date: Fri, 13 May 2005 16:45:48 -0400	[thread overview]
Message-ID: <da8784a6766d1a5ca1e29100fe7ac20e@coraid.com> (raw)
In-Reply-To: <77ea6b7c9988149c674429387f842122@plan9.ucalgary.ca>

>> or no, depending on the file server.
>> it's not really a well-formed question now that i think about it.
>> 
>> devpipe preserves message boundaries.
>> il does too.
>> tcp does not.
>> 
> 
> "Plan 9 from Bell Labs" discusses message boundaries briefly in the
> context of 9p:
> 
> "The 9P protocol must run above a reliable transport protocol with
> delimited messages.  9P has no mechanism to recover from transmission
> errors and the system assumes that each read from a communication
> channel will return a single 9P message; it does not parse the data
> stream to discover message boundaries.  Pipes and some network
> protocols already have these properties but the standard IP protocols
> do not.  TCP does not delimit messages, while UDP [RFC768] does not
> provide reliable in-order delivery."
> 
> those may not be the same message boundaries Ishwar was looking for
> though.

Do you mean 9p requires message boundaries to function, or is it part
of the protocol?  9p2000 doesn't need it to work, like the previous
version of 9p did.  It's not part of the protocol, since it would be
the transport's job.  Each 9p2000 message has a length field for the
message.  Old 9p didn't and you had to use il or some extra cruft to
get message boundaries over tcp.



  reply	other threads:[~2005-05-13 20:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13 18:21 I RATTAN
2005-05-13 20:02 ` Russ Cox
2005-05-13 20:04   ` Russ Cox
2005-05-13 20:14     ` andrey mirtchovski
2005-05-13 20:45       ` Brantley Coile [this message]
2005-05-13 20:55       ` I RATTAN
2005-05-13 21:09         ` Ronald G. Minnich
2005-05-13 21:48     ` "Nils O. Selåsdal"

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=da8784a6766d1a5ca1e29100fe7ac20e@coraid.com \
    --to=brantley@coraid.com \
    --cc=9fans@cse.psu.edu \
    /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).