OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [cmis-comment] browser status code


Hi Michael,

Returning the status code 200 here was a deliberate decision.
This binding is intended for applications running in a web browser. Some browsers do not trigger an Ajax callback when the server sends the status code 204. That is, such _javascript_ applications would never know if the call was successful or is still running.
I agree that from a design perspective returning 204 would be more appropriate, but it’s better to have a specification that works in the real world than being correct everywhere.


Regards,

Florian




From: Michael Brackx <michael.antispam+cmis@gmail.com>
Date: Freitag, 21. März 2014 18:02
To: "cmis-comment@lists.oasis-open.org" <cmis-comment@lists.oasis-open.org>
Subject: [cmis-comment] browser status code

Hi,

Currently actions with an empty response return status code 200.
For example deleteObject (5.4.3.20).
Would it not be more appropriate to return 204 No Content?

Please consider this change for the next version of the spec.

Michael


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]