From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9P writes for directories
Date: Thu, 26 Mar 2009 14:44:53 -0500 [thread overview]
Message-ID: <a4e6962a0903261244t52fa55a1y8e90d45dc5ac3905@mail.gmail.com> (raw)
In-Reply-To: <584ACAD1-5343-4656-AEBC-8C0BFDD5724C@sun.com>
On Thu, Mar 26, 2009 at 2:31 PM, Roman Shaposhnik <rvs@sun.com> wrote:
> On Mar 21, 2009, at 12:00 AM, Roman Shaposhnik wrote:
>
> The story here is that we are building a bunch of RESTful APIs
> and my personal preference is to bend HTTP as close to 9P
> as I can get (for obvious reasons). Now, the closest match
> to "create" would be POST with a metadata payload on a
> "subdirectory" URI. But of course, it is not a create at all.
> It really is much closer to write on a subdirectory. Hence the
> question: is there anything that HTTP makes us lose except
> for the transactional nature of create?
>
So, my understanding is the function of POST to a collection/directory
was to create a new entry in the collection where the ID is assigned
automatically by the collection. The ID created is typically returned
by this operation.
This actually sounds more like a (devip style) clone operation to me.
Outside of the ID bit, why wouldn't create suffice?
-eric
next prev parent reply other threads:[~2009-03-26 19:44 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 [this message]
2009-03-26 20:23 ` Roman Shaposhnik
2009-03-26 20:52 ` erik quanstrom
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=a4e6962a0903261244t52fa55a1y8e90d45dc5ac3905@mail.gmail.com \
--to=ericvh@gmail.com \
--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).