... Yes, or it could be <product xlink:href="/products/1" /> or <product xlink:href="/AD5EFFAE132865DDE" /> or whatever. ... Exactly! ... It's tempting to...
Today we have prepared the initial version of semap RESTful API [1]. It was very interesting work for us, because we didn't see any similar approaches how to...
... I *would* suggest that it is implemented that way. It’s the hypermedia constraint. Truly RESTful apps are – by definition![1] – designed around the...
... Yeah, not sounding terribly convincing to me. I do think your described solution is fine, as long as there really isn't a need for 'machine to machine'...
... URIs simply *are* opaque, whether we like that or not. ... I disagree. Somewhere the client will have to have it "explained" to it how to either construct...
... No, they're not. Apart from the obvious things such as scheme and host for http uri's, which can reliably derived from uri's there are other uses mentioned...
... All of which are specific uses at specific points. ... And it may or may not work. All a processor *knows* about the URI http://example.org/weather/Chicago...
Jon Hanna ... I don't get this. Is the processor in your example server-side or client-side? If server-side, then it's all true what you write, but uri opacity...
... Doesn't matter. Indeed, one of the cases where opacity is of most importance is when a proxy cache is deciding whether a request can be served from the...
I am just starting with REST and don't know which is the proper way to model this. I have a resource "booking" that can be cancelled. Cacellation just sets a...
Hi all, This issue in Restlet in now fixed in SVN and will be part of the upcoming 1.0.6 release. Best regards, -- Jerome Louvel http://www.restlet.org...
... DELETE + 301, I guess. ... If you have flags other than some kind of “active/not active” status, probably by exposing them as separate resources for...
... With that apporach we would have for example DELETE /bookings/{id} ... 301 Moved Permanently Location: /cancelled_bookings/{id} and /bookings/{id} wouldn't...
... I meant that you would return 301 for subsequent requests to /bookings/{id} – not in response to the DELETE itself. A DELETE doesn’t have to result in...
... Good. ... Ahhh, it starts to take shape. Thanks so much! So, in that solution /budgets/{id}/approved becomes a resource. That could be a RW atrribute just...
Hello REST crowd. I've just discovered this group few days ago and immediately found it interesting. I'm new to REStful architectural style approach of...
Inherent to message-based architectures is the inclusion of operations in the message. I use message-based architecture here, because I see it as being...
Is there a restful convention for creating or changing association attributes that relates resources to each other? I'm specifically wondering in the case...
Hi amaeze77, ....got a real name we can use? ... If you do that you are *not* implementing a RESTful system. ... It looks like you are digging around in the...
... OK, assuming that /activities/18 and /subjects/5 already exist then I would assume: PUT /activities/18 updates the existing activity 18 resource PUT...
... Yes, I see no problem with that -- just use POST on the collection URI that represents the class for which grades are being posted. A CSV format is good...
... No, it should just be the association. That's the key: the relationship *is* a resource all to itself. Same with a transaction (the example in the REST...
... [...] ... I presume that you would make it so if you wish that it be so. ... The "DELETE" request seems entirely appropriate to me. Why do you think that...
... Tunneling operations through POST breaks REST's uniform inerface constraint. You end up with client and server being coupled on the operation semantics. ...
Thanks Karen and Etan for responding, I've replied to both of your comments in this post: ... Well right now (the way I've implemented it) that url will update...
Thanks Roy for your advice. So, what would be the correct HTTP response code in case of "partial grade upload" using POST interface? For example, let's say we...
... You could return a representation of the state of the grade list after processing the request. You would indicate that it was a representation of the list...
... Which is okay, as long as you don't mind an update that doesn't update anything. If you want to be able to just create the association you want to expose...
Is it just me or do all these discusions about URI form and pattern seem to put undue emphasise on URI composition at the expense of hypermedia-driven...