9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9p flush
Date: Thu,  9 Mar 2006 19:03:38 +0000	[thread overview]
Message-ID: <cfe218816d9a0282163e493777b2a1cb@vitanuova.com> (raw)
In-Reply-To: <f5684a847374515f64425b1adb81bba8@swtch.com>

> It is more important to get the semantics right than the timing.

that's good.

my particular scenario is that i'm writing a 9p server that is also a
9p client.  if a particular request is flushed, then the process
dealing that request needs to be able to send a flush request down the
client 9p connection, and wait for a reply in order to decide how to
reply to the original flush request.

as far as i understand it, this should be fine.

flush is such fun.



  reply	other threads:[~2006-03-09 19:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09  6:54 [9fans] web site being down & reliability Russ Cox
2006-03-09 18:30 ` [9fans] 9p flush rog
2006-03-09 18:40   ` jmk
2006-03-09 18:55   ` Russ Cox
2006-03-09 19:03     ` rog [this message]
2006-03-09 18:59       ` Ronald G Minnich
2006-03-09 21:37 ` [9fans] web site being down & reliability Russ Cox

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=cfe218816d9a0282163e493777b2a1cb@vitanuova.com \
    --to=rog@vitanuova.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).