As I understand it, MoST is a data driven standardised interface. Stuck to xml. But I've allway understood ReST in this way. if you get a uri, you receive a...
... The URI addressability of node-ids is what you need to standardize - the mapping between local data (an element in an XML document) and remote resources (a...
From: "S. Alexander Jacobson" <alex@...> ... <deleted> Okay. I really must not be grasping what you are saying about REST vs MoST. It seems to me that MoST...
... I am saying that if YOU know the schema of the resource that should be all you need to have have a client interacts with it using HTTP. You shouldn't need...
From: "S. Alexander Jacobson" <alex@...> ... So you are saying that I should be able to have an uber-client that would know how to act with *any* resource...
Yes, the echo/atom API work is in fact what started me thinking about MoST. My point is that we should not need an Atom API and a RSS API and a Wiki API and a...
From: "Alex Jacobson" <alex@...> ... its ... I disagree. For instance, if a resource is an JPG image and someone attempts to PUT a PNG image, without even...
Ok. I was making a semantic/architectural point but your point about '#' is completely valid. Any reason not to replace '#' with ';'? More to the point, any...
If 415 means only that the server doesn't like the content-type header, its a pretty worthless status code. Following ward cunningham's FIT model for...
... Even in the latter case, I'd say it's just fine. If your application only consumes well formed XML on POST, then you *may* want to use 400, but 200 would...
... Sure, in that case your resource is just an XML parser, not an application that consumes well-formed and perhaps valid XML. ... the ... is ... happened. ...
... Agreed. If the state was transferred such that it was "processed", then it's a success. One can, I believe, quite reasonably define "processed" to...
Okay... now we are up to: 400 or 403 or 409 or 415 (or sometimes 200) I am unsure about using 415, though. If someone POSTs/PUTs an "text/xml"; request entity...
Seairth, I just took a look at your blog and your comments on Jot/ReSTful blog architecture and at RNA <http://www.seairth.com/blog/industry/49> and ...
Why isn't the correct response 415 (Unsupported Media Type)? Your application requires that the POST conform to a particular schema and that schema has been...
... It seems that this is just a shortcoming in HTTP. 4xx is for client errors. We are definitvely talking about a client error. In the absence of a more ...
... JR> So you think this is wrong because WebDAV added a new status code? I can't JR> agree -- the whole point of WebDAV is to *extend* HTTP/1.1 (with new JR>...
... So you think this is wrong because WebDAV added a new status code? I can't agree -- the whole point of WebDAV is to *extend* HTTP/1.1 (with new methods,...
... I just don't think that it is a WebDAV specific problem, so I would expect WebDAV to use whatever status would be appropriate for any other HTTP...
Mark, ... Well, in my *inexperience* that looks like a loss of visibility. I understand syntax error to be a condition that aborts meaningful processing, and...
So far, all I am seeing is that just about everyone has a different take on whether to use 400, 403, or 409 (and maybe even 200 for POSTs). I realize that...
Hey Walden, ... b, I'd say, keeping in mind that "successful data processing" can include the determination of some "invalid" information within that data,...
Mark, What would you be telling intermediaries if you used 200 to reply to a POST of some malformed content: a. that something was successfully appended or...
... RFC2616 says: "The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications." ...
Ah, Seairth was asking *that* question. I didn't realize. We should add this to the FAQ, as we've had this twice before I think. Sometimes it's 400,...
... a ... talks ... it ... Well all 4xx codes indicate a problem with the request. Have you got a specific example? Do you mean something like missing required...
That's what I thought, except when I was working on Jot (my RESTful blog system) someone (forgot who) said that 400 indicated a problem with HTTP layer itself...
