From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9P writes for directories
Date: Thu, 26 Mar 2009 16:52:49 -0400 [thread overview]
Message-ID: <eb342b7cd1fbc63ff025599ce7d63408@quanstro.net> (raw)
In-Reply-To: <C7722C98-E353-4786-BD23-499706F43148@sun.com>
> It would (just as Erik pointed out). I guess I was just looking for
> symmetry (if POST is really a write(*), it should translate into write
> independent of whether the URI corresponds to a subdirectory or
> not) and potential pitfalls that made 9P spec disallow writes on
> subdirectories (and since nobody can identify any of those -- I'll
> rest my case and proceed with translating POST into different
> 9P messages depending on the type of the URI).
the only thing that write and create have in common
is the fact that they both translate to 9p messages.
the beauty of create is that it is atomic. if you don't
care about atomicity, you can just open if create fails.
using write, the qid could not be returned and there
would always be a race. since one would not have the
qid, it would be impossible to tell if the race had been
won.
- erik
next prev parent reply other threads:[~2009-03-26 20:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 7:00 Roman Shaposhnik
2009-03-26 19:31 ` Roman Shaposhnik
2009-03-26 19:35 ` erik quanstrom
2009-03-26 19:50 ` Roman Shaposhnik
2009-03-26 19:56 ` erik quanstrom
2009-03-26 19:44 ` Eric Van Hensbergen
2009-03-26 20:23 ` Roman Shaposhnik
2009-03-26 20:52 ` erik quanstrom [this message]
2009-03-26 20:54 ` Eric Van Hensbergen
2009-03-26 22:05 ` Roman Shaposhnik
2009-03-28 1:36 ` Uriel
2009-03-28 4:03 ` Roman Shaposhnik
2009-04-19 16:43 ` Enrico Weigelt
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=eb342b7cd1fbc63ff025599ce7d63408@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).