9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Cc: russcox@gmail.com
Subject: Re: [9fans] 9p2000 query
Date: Fri, 13 May 2005 15:09:50 -0600	[thread overview]
Message-ID: <Pine.LNX.4.58.0505131509130.7051@enigma.lanl.gov> (raw)
In-Reply-To: <Pine.GSO.4.58.0505131646310.25968@cps211.cps.cmich.edu>



On Fri, 13 May 2005, I RATTAN wrote:

> client on A sends a request (message), wsits for reply to come back
> can server process pickup the request with single read operation

that is totally dependent on transport, right? for tcp, you have to do a 
little work. That's why the byte count at the front of the 9p2000 messages 
is so nice.

ron


  reply	other threads:[~2005-05-13 21:09 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
2005-05-13 20:55       ` I RATTAN
2005-05-13 21:09         ` Ronald G. Minnich [this message]
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=Pine.LNX.4.58.0505131509130.7051@enigma.lanl.gov \
    --to=rminnich@lanl.gov \
    --cc=9fans@cse.psu.edu \
    --cc=russcox@gmail.com \
    /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).