From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9p and how can I know when a write is finished
Date: Wed, 1 Mar 2006 11:31:26 -0500 [thread overview]
Message-ID: <f749e3e512902abbc23842273b38673d@plan9.bell-labs.com> (raw)
In-Reply-To: <3acfc358add926f6e589cb9faaf299fa@vitanuova.com>
On Wed Mar 1 10:57:01 EST 2006, forsyth@vitanuova.com wrote:
> >>Wrong, the Tclunk is not warranteed to arrive any time soon.
> >>Tclunk != close()
>
> > In the end you are on the safe side when waiting for Tclunk.
>
> i think it's sad not to implement close [or equivalent] -> Tclunk in a timely way,
> and indeed in an orderly manner (wrt the same client process),
> at least for files, and especially for files with DMEXCL.
The shadowy '9P Dubious Protocol Enhancement Committee' will
perhaps consider that at their next secret meeting.
next prev parent reply other threads:[~2006-03-01 16:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 14:29 Gabriel Diaz
2006-03-01 14:49 ` Sape Mullender
2006-03-01 15:14 ` [9fans] " Gabriel Diaz
2006-03-01 15:15 ` [9fans] " Anselm R. Garbe
2006-03-01 15:20 ` uriel
2006-03-01 15:29 ` Anselm R. Garbe
2006-03-01 15:49 ` Gabriel Diaz
2006-03-01 15:57 ` C H Forsyth
2006-03-01 16:31 ` jmk [this message]
2006-03-01 16:47 ` Russ Cox
2006-03-01 22:55 ` Dave Eckhardt
2006-03-01 22:59 ` rog
2006-03-01 23:06 ` Ronald G Minnich
2006-03-01 16:58 ` Ronald G Minnich
2006-03-01 17:21 ` uriel
2006-03-01 17:19 ` Ronald G Minnich
2006-03-03 1:49 ` uriel
2006-03-03 2:34 ` Ronald G Minnich
2006-03-03 21:26 ` David Leimbach
2006-03-01 17:29 ` Russ Cox
2006-03-01 17:41 ` Paul Lalonde
2006-03-01 19:48 ` Ronald G Minnich
2006-03-01 19:58 ` "Nils O. Selåsdal"
2006-03-01 20:16 ` uriel
2006-03-02 1:45 ` erik quanstrom
2006-03-01 18:50 ` Latchesar Ionkov
2006-03-01 18:55 ` uriel
2006-03-01 17:21 ` Gabriel Diaz
2006-03-01 17:22 ` Ronald G Minnich
2006-03-01 18:10 ` rog
2006-03-01 19:49 ` Ronald G Minnich
2006-03-01 20:15 ` rog
2006-03-01 17:59 ` Skip Tavakkolian
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=f749e3e512902abbc23842273b38673d@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.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).