i am resuming this thread also for the deletion use case in OS 2.5,
where a user would like to delete at once an entire group-Id (meaning
to delete the related relationships with all the users under this
group-Id).
as i would expect it this could be handled by leaving the payload body
empty (currently a person object is mandatory).
re DELETE bodies, some http stacks do not allow or provide the body of
DELETE requests, thus limiting the implementation of the spec. As an
alternative design one could follow the pattern
REST-URI-Fragment = "/people/" Initial-User-Id "/" Group-Id "/"
Related-User-Id
, which already exists for GET and could apply to DELETE as well.
This way DELETE body could be empty and the design could accomodate
both the single user deletion use case and the "entire list" use case
(by simply omitting the Related-User-Id).
any hint?
thanks
walter
On Aug 8, 12:29 pm, Laurent-Walter Goix <laurentwalter.g...@gmail.com>
wrote:
> hello all,
> current trunk spec of the social-api-server allows for creating a
> person and/or relationship, but does not allow for creating multiple
> at once. this would help managing lists of users (eg already existing
> in some other system) altogether
> i can understand this as a potential batch request but it may also be
> "simply" addressed by supporting Person array/collection in the body
> of POST (and/or PUT for update/replace) ...Of course whenever an error
> occurs on a single person of that collection a default behaviour
> should be defined (e.g. ignore single or reject all)
> i could also see this useful for activities, to manage multiple at
> once.
> is there any interest on this feature and how it can be best
> addressed?
> thanks
> walter
