Closed mmarum-sugarcrm closed 10 years ago
From mgmarum@gmail.com on March 15, 2013 14:36:22 I think it is reasonable for DELETE to allow the Id to be specified in URI OR in the request payload.
From laurentw...@gmail.com on March 26, 2013 16:03:52 attached is a patch that allows the Related-User-Id to be included optionally both in the DELETE and PUT URIs. It also allows DELETE request payloads to be empty and adds some text clarifying the various options further providing a couple of examples.
(btw the patch also fixes minor HTTP headers in other examples)
From rbaxte...@gmail.com on March 27, 2013 21:40:20 Walter could you add draft tags around the section you changed?
From mgmarum@gmail.com on March 29, 2013 20:28:42 I can add them.
From mgmarum@gmail.com on March 29, 2013 21:43:39 Patch applied in r1713.
+1
Original author: laurentw...@gmail.com (October 23, 2012 16:01:43)
Ref. Social Server API section 2.1.4.
In OS2.0.1 only “@self” was supported. OMA expanded this support to other Group-Ids, which were also introduced by OS2.5. however, a discrepancy applies now to identify the single “id” of the Person/relationship to be removed. OMA has chosen the way of adding an optional ["/" Related- User-Id] at the end of the request uri with no payload in the body of the DELETE (or ignored if present), whilst OS2.5 now requires a person object as payload. We chose the request uri way because:
[1] https://groups.google.com/d/topic/opensocial-and-gadgets-spec/fpQMG3scvd0/discussion
Original issue: http://code.google.com/p/opensocial-resources/issues/detail?id=1327