3 ms·
Your headline of "...this is poor API Design" is clearly not written as here's a "REST-ful alternative to using POST for large queries". There's a strong case
by mythz 12y ago
Your headline of "...this is poor API Design" is clearly not written as here's a "REST-ful alternative to using POST for large queries".
There's a strong case for taking advantage of every technology at your disposable to deliver the most compelling value and end-user experience possible, as-is the trait/focus of successful companies (ala DropBox).
And how exactly is REPORT better for linkability? Why is being able to link a 8kb QueryString more important and worth sacrificing over all other end-user features/qualities for? and what are other examples of "breaking the web"?
- treve 12y agoREPORT definitely still has the linking problem. REPORT only solves the issue that POST is unsafe/non-idempotent. This is just a marginal improvement, and would not qualify as restful. The 'creating a query resource' would be an option for those that do want a linkable resource. Why linking is important? I don't think I can quickly sum that up in a comment, or properly do it justice. If you're genuinely interested I would be happy to look for and suggest a few resources that do a much better job than I ever could. Regardless, I don't believe that HATEOAS/RESTful design is the be-all and end-all. I think certain web api's are particularly well-suited for it, but it's a type of design that is not appropriate for every problem.
- modarts 12y agoOh man, I love ServiceStack and have built some incredible API's on it. Just wanted to say thanks :)