Which HTTP code is proposed as the code for Operation Failed?
-Rory
On 26 Oct 2009, at 10:34, Sebastian Negomireanu wrote:
Well, in my opinion it doesn't really matter if you send the ok or
not, but
in the end I think the API should be consistent. Either you return
ok on all
calls that don't retrun documents, or you use the HTTP status code
on all.
Otherwise you make it more difficult for programmers to use it.
Best regards,
Sebastian Negomireanu | CTO / Managing Partner JustDesign Sibiu,
Romania
+40-726-181186 | +40-788-757462
[email protected]
SC JustDesign SRL | Str. Dorului 20, 550352, Sibiu, Romania
+40-269-210008 | [email protected] | www.justdesign.ro
-----Original Message-----
From: Nils Breunese [mailto:[email protected]]
Sent: Monday, October 26, 2009 10:06 AM
To: [email protected]
Subject: RE: COPY bug
Doesn't the HTTP status code already tell you whether the request was
successful or not? What does sending a bit of JSON add to that?
Nils.
________________________________________
Van: [email protected] [[email protected]] namens Chris Anderson
[[email protected]]
Verzonden: zondag 25 oktober 2009 23:58
Aan: [email protected]
Onderwerp: Re: COPY bug
On Sun, Oct 25, 2009 at 12:54 PM, Paul Davis
<[email protected]> wrote:
Hmmm. Now all we have to do is decide if we want ok:true or not.
Anyone have an opinion? It would remain more consistent with the
other
CRUD style operations that don't return a document.
I think "ok" : true is what we want here.
De informatie vervat in deze e-mail en meegezonden bijlagen is
uitsluitend
bedoeld voor gebruik door de geadresseerde en kan vertrouwelijke
informatie
bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of
verstrekking
van deze informatie aan derden is voorbehouden aan geadresseerde. De
VPRO
staat niet in voor de juiste en volledige overbrenging van de inhoud
van een
verzonden e-mail, noch voor tijdige ontvangst daarvan.
