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
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 "/"
, 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).
On Aug 8, 12:29 pm, Laurent-Walter Goix <laurentwalter.g...@gmail.com>