OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [xdi] Regarding $put / $set

+1. I read up on it a little and this Quora answer RE the difference between HTTP PUT and POST really does nail why we should be using the equivalent of HTTP PUT for writing to the graph.

While I like the alignment with HTTP verb PUT, in terms of the XDI protocol I would prefer $set. How do others feel?


On Sun, Apr 14, 2013 at 5:12 AM, Markus Sabadello <markus.sabadello@xdi.org> wrote:
I found this old message on the XDI TC:

At that time I felt XDI needed exactly what Joe Johnston and Peter Hizalev of Respect Network described on a recent call:
An XDI operation that either adds something to the graph, or modifies what's already there, i.e. a combination of the $add and $mod we have now.

This would have the following advantages:
- As an XDI client developer, you wouldn't have to care whether a context node or relation or literal already exists in the graph or not.
- It makes it much easier to implement highly scalable backends for graph storage, based on principles such as Eventual Consistency and Optimistic Replication.
- This operation would align perfectly with HTTP's PUT verb.

Doesn't matter whether we call it $put or $set, same thing, but it seems worthwhile to pick up this topic again on the TC.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]