3 ms·
Excellent point. I can't agree more. In the long run, this makes things far more flexible. Also, I might be nitpicking here, but I think the difference between
by mikegirouard 14y ago
Excellent point. I can't agree more. In the long run, this makes things far more flexible.
Also, I might be nitpicking here, but I think the difference between a URL and a URI is that the URL explicitly defines the media type.
If that's the case, then the advice would be to use URIs pointing to resources in combination with `Accept` headers.
- icebraining 14y agoAlso, I might be nitpicking here, but I think the difference between a URL and a URI is that the URL explicitly defines the media type. No, no. An URL is an URI. And the URL doesn't define any media-type, those are hacks created frameworks; there's no such thing in the spec.