Hello again. After reading some interesting posts about REST, specially [1] REST APIs must be hypertext-driven [2] Describing RESTful Applications I started to...
... Yes. You might also want to check whether at any point you rely on the specific structure of your URIs in your clients, e.g. the first part of the URI, or...
Yes, that's great step in the right direction. Most so called RESTful services even fail at that level. What you're doing is augmenting your plain old XML...
... Roy's blog post entitled "REST APIs must be hypertext-driven" [1] seem to indicate that documents are just that: documents. Their purpose is discovered by...
... That is a misinterpretation. The idea behind using concrete media types is to keep the interactions visible, i.e., we should be able to apply some amount...
... Sorry, but can you clarify if you simply don't agree with my interpretation or if you *know* that my interpretation is wrong? ... That can also be achieved...
... See RFC 2616#7.1 and 14.17. Entity headers like Content-Type provide metadata about the entity. What a given media type means is something clients and...
The REST Wiki [1] seems to be down again. In fact, I believe the number of times I've tried to access it and it's been down or unbearably slow far exceeds the...
Any reason you wouldn't want to move the contents to http://restpatterns.org? It's hosted on a scaling EC2 cluster with 24/7 monitoring [1] and the wiki is...
... I didn't author or edit a single page there, so it would not be for me to decide. ... That sounds great. ... I admit that I would feel a little more...
... Yeah, that would be my opinion too. And Roy's words: "A REST API should spend almost all of its descriptive effort in defining the media type(s) used for...
... Steve - that is what I was referring to as the misinterpretation. Contrary to what you are saying, media types encourage shared formats. In the absence of...
... Nope. If you read my previous response on tunneling and Dare's post, it is the opposite of what you are saying. ... Can you explain how came to that...
... Conclusion is a strong word. That's more the way I'm leaning currently. Regardless, this exchange has motivated me enough to finally commit some of my...
... This is the same discussion as DSLs vs. general purpose programming languages, or internal DSLs vs. external DSLs, or UML vs. MOF, or a specific XML format...
Sorry, if this topic has already been discussed. Searched the list but couldn't find a concrete answer, so shooting my question here. For performance reasons,...
Hello again: First let me thank you guys for all the answers. I think the first part of my post is well answered, regarding the use of hiperlinks as attributes...
Hello Rama, ... Why not just do these two GETs, and cache the representations if performance is an issue? It seems to me that conflating two logically ...
... I don't see why this is a bad idea. What would be the downside of creating new resources? I think resources can be created cheaply enough so that a generic...
... In my understanding, it refers to defining new media types such as "application/atom+xml". ... Yes, although I found it easier to interpret Roy's remark in...
... I think this is matter of decoupling vs. cohesion, i.e. if a meaningful application would need to understand the "customer" and "account" entities, you...
Yes, that's what I was thinking right now, but then why don't use just Content-Type: application/xml;type=vnd.bank.org.account instead of "creating" a new...
Or even more straightforward, Content-Type: application/xml;type=http://www.mycompany.com/schemas/bankaccounts.xsd ... type" at all? ... the same resource, as...
... I'm with Steve here. I mean, if we're trying to stick to the specs, how about http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7 : "Use of...
... Steve - allow me to refer back to my previous comment that there is yes/no answer to this question. You seem to be alluding that it "incorrect" to create...