3 ms·
Could you elaborate? My limited experience with WebDAV is what Subversion uses it for, and I've always had the impression that the PROPFIND-type of verbs could
by skrebbel 13y ago
Could you elaborate? My limited experience with WebDAV is what Subversion uses it for, and I've always had the impression that the PROPFIND-type of verbs could just as well be expressed as GET operations on a "property" resource type. I've dismissed WebDAV as "not getting the point" since, but your comment gives me the feeling that that might've been too quick a conclusion.
What's the good parts of WebDAV and how do they help me make decent RESTful APIs?
- grandalf 13y agoRFC4918 is where lots of the status codes people often throw into "REST" APIs came from... http://datatracker.ietf.org/doc/rfc4918/?include_text=1 http://datatracker.ietf.org/doc/rfc4918/?include_text=1 I'm not a big fan of this practice b/c I've found that as APIs evolve the status codes end up having application specific meaning rather than standard, protocol specific meaning. Bottom line, I think that unless your API very closely resembles the kind of thing WebDav is designed to do, it's better to just do a simple REST version with core HTTP status codes and handle any standardized response semantics inside the response body.