Hi, I am just getting into this REST thinking, and kicking around theoretical questions and basic puzzlers seems to help tremendously in getting the thinking...
... What if my resource is the list of server log entries? I know I am getting into nitpicking here, but this is a mission of learning for me, so nitpicking is...
... Going back to what RFC 2616 says (in section 9.1.1): "Naturally, it is not possible to ensure that the server does not generate side-effects as a result of...
... Then you could have a RESTfull interface to it. But a server log entry's production would not be part of the RESTfull interface since the log is coming...
The safety of GET is not an interoperability requirement (and therefore not a MUST), since the client still gets their data if the server changes state as a...
Hi all, When you're passing representations around - let's say you have defined some XML dialects - should you err on the side of defining new MIME types for ...
In my experience, we had a specific XML-based file type that, when downloaded by the user, needed to be opened in a specific application. Initially we tried...
Hmmm. There have been long and noisy discussion about how user agents should handle content with a specified content-type. Some developers want the client...
... A new media type is the only way to maintain self-descriptive messages. ... Probably a good idea. Better would be "don't do that". 8-) ... The issue is...
Is it a great sin if a server implementation does something like this: GET /test/test.html returns Content-Type: text/html GET /test/test.html?type=xml return...
... Neither feel good to me, If a resource is HTML, then you should it's content-type should be HTML. If it's some XML other than XHTML or well-formed HTML...
... HTML is only sometimes XML. If the HTML has one of the W3 DTDs it is likely that it is not XML compliant. Having said that, it is possible to produce...
... I probably should've stated more clearly in my original post: the body of response is indeed XHTML. I am trying to work around a very specific issue, which...
here's some ideas to share.. In the _ideal_ REST world, a good resource identifier, URL should not contain representation-specified information, "Accept"...
... It's quite obvious as Jan said, a better alternative would be providing a search form, ex. https://example.com/Customer/searchForm and use to POST plus...
... This is all very good advice. Remember though, that REST is *really* useful for webservices where HTML is not an issue. If you're designing a web...
... Yes, the entire HTTP interaction is encrypted when running over SSL. The URL is still displayed in the browser, though. And of course the entire request...
Currently, I'm working on a PHP5 framework which implements REST in design. Hopefully, it will provide an easier way to build RESTful web applications. The...
I've noticed these cases are not the correct way to deal with content negotiation after started to read HTTP/1.1 spec in details yesterday. i'm now seeking for...
... Could you post the details of your research here? I am very interested in this topic, as well. ... The browsers don't, but the XMLHttpRequest allows that...
... i'm doing a study on practical REST implementation in current web application. IMHO, it might be a good start to introduce REST to public, by showing...
... In what way were the scenarios you outlined incorrect? ... I'd say Accept is the way to do it... but a browser is primarily an HTML rendering tool. I'm not...
... I'm still trying to study more details about content negotiation in HTTP/1.1 But as far as i know now, an appropriate way for server to handle Accept tag...
