On Thu, Mar 26, 2009 at 2:31 PM, Roman Shaposhnik <r...@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
