From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Another Pathological 9P question.
Date: Tue, 5 Aug 2003 23:49:07 -0400 [thread overview]
Message-ID: <81fa2b18c107a916b7871286a87ccac9@plan9.bell-labs.com> (raw)
In-Reply-To: <200308051250.h75CoS706174@augusta.math.psu.edu>
On Tue Aug 5 08:51:19 EDT 2003, cross@math.psu.edu wrote:
> Okay, here's another question: if I initiate a request on an open fid, such
> as a read, and then clunk the fid immediately afterwards but before getting
> a reply for the read and without flushing the read, what should happen?
> Should a clunk implicitly do a flush for all outstanding transactions on a
> fid, or should the read complete normally?
>
> - Dan C.
The client would be in error by telling the server that the file
represented by the fid was no longer needed when it clearly is.
However, most server implementations complete the read normally.
prev parent reply other threads:[~2003-08-06 3:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 12:50 Dan Cross
2003-08-06 3:49 ` jmk [this message]
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=81fa2b18c107a916b7871286a87ccac9@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).