I agree, 404 seems the right code for this. Http talks about "resources":
when an internet browser returns a 404 is because the specified resource
you are asking for couldn't be found on the server, which is exactly the
same use case Bert said (the resource you are trying to delete was not find
on the server).
El 17/1/2015 2:19, "pazospablo at hotmail.com" <pazospablo at hotmail.com>
escribi?:
> Hi Bert, that's a REST Web Services convention. REST reuses a lot of the
> HTTP infrastructure, like methods, status codes, sone headers, etc.
>
>
> Sent from my LG Mobile
>
> ------ Original message------
>
> *From: *Bert Verhees
>
> *Date: *Fri, Jan 16, 2015 8:18 PM
>
> *To: *For openEHR technical discussions;
>
> *Subject:*CRUD Restlet
> I was looking at EHRScape, I should have posted this question there, but
> the Community-page does not show any communication-means, only adds.
>
> And maybe the question is also generic and are more people thinking about
> this.
>
> I am wondering about the HTTP-errors, they seem to be used for
> communicating application-errors.
> I think this could be an error.
>
> For example, if you look at the: DELETE /demographics/party/{partyId}
>
> It can return a 404 with explanation: 404 Not found - the specified party
> was not found (DEMO-6021).
>
> I think this is possible wrong, because on HTTP-level the call was an
> success, and should therefor return 200, meaning, the request is received
> and understood, and processed.
> In the return-message it should IMHO, if necessary the result and
> error-message on application level.
>
> Someone thoughts about this?
>
> Thanks
> Bert
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150117/7a890941/attachment.html>
