Roy Fielding mistyped (ha!) a word in one of his playful messages<http://tech.groups.yahoo.com/group/rest-discuss/message/15023>; ... Ah, yes, a similar thing...
I am working on a Blog project where I use ATOM for representing feeds and blog posts. I have a set of draft posts and published posts. In order to change a...
POST a text/uri-list with the blog posts you want to publish? ... POST a text/uri-list with the blog posts you want to publish? On Mon, May 10, 2010 at 8:30...
Hello Jorn, What do you think of? POST /drafts (+ post content) ... GET (previous location header) ... POST (following the link 'publish') ... So you do not...
... I consider the 'empty' POST to the publish URL as a little too RPC like. I would rather post a text/uri-list to a resource that is linked with relation...
... Except that your introduction of a publish URL is one step better than assuming a specific sub-resource. Thanks! So a more general solution is: if you have...
... Sorry, Im pretty bad with the difference between verbs and nouns in english as its my second language. The correct relation name would be "publication"....
... Aha ... this would make the "publication" (or rather "publicationS") resource a list of "transaction objects" - objects representing operations that have...
... resource a list of "transaction objects" - objects representing operations that have taken place. Actually, in a lot of systems, every resource list is a...
... AtomPub has native support for that use case: http://tools.ietf.org/html/rfc5023#section-13.1.1 Use <app:draft/> to mark the posting as draft and simply...
... Yes. It is an anti-pattern because the message is not self descriptive. See http://www.nordsc.com/blog/?p=414 Jan ... Jan Algermissen, Consultant NORD...
... Yes. It is an anti-pattern because the message is not self descriptive. See http://www.nordsc.com/blog/?p=414 Jan ... Jan Algermissen, Consultant NORD...
... http://tools.ietf.org/html/rfc5023#section-13.1.1 Oh, cool. Thanks. But ... then we are back to the situation where I must POST my whole resource in order...
I'm sure this has been covered in the past, but I missed it... what are some general guidelines for giving a client hints about what sort of data to supply to...
... You've selected to build on top of a pretty inefficient style, so it's to be expected I suppose. ... It seems to me that it's just changing the resource...
IMO, this boils down to one of three options: 1) resend the entire representation (via PUT /{existing-item-uri}) back to the server w/ the "status" data...
(3) is the one I am gravitating towards. It expresses exactly what I want and in addition to this it also serves as a source of the history of the resource -...
... longer than you want the client to have to wait for an initial response. I like to return a 202 Accepted status in this case, complete with a link to a ...
... Which makes me wonder if this is related only to status changes. I think it's a more general pattern: whenever you expect that the processing of a...
... Hash: SHA1 ... I believe one should be able to assume that the content type of the representation returned from a server from GET for URI is acceptable in...
... Hash: SHA1 I put down some thoughts on the application of REST principles to programming (and how I've applied those in the Persevere framework), if anyone...
... GETting the schema URI returns a schema, but in which media type+profile is this schema described? Conneg can be done as usual with this GET, but the same...
Hi, I wanted to have the groups opinion on the http://googlecode.blogspot.com/2010/03/making-apis-faster-introducing-partial.html Sounds very attractive but...
Hello Mike! ... /status-changes/) back to the server using the appropriate media type. Did I miss something or is it the suggestion I made? If so, ++ on this...
Hi Guilherme! <snip> Can you help me to identify the representation size influence? (I can see we need a handy patch media type to do 2, but if its present, I...
... From a very brief look: Sounds somewhat ok, here is what is missing: - a link relation (or other hypermedia control) that defines the implied URI template...
Partial updates use atom with PATCH and seems nice. I just dont personally like too many query parameters and URL patterning them with GET, even less with POST...
