5 ms·
Because it's harder to set the content-type from browsers. Perhaps if your API won't be that useful to browser based clients, perhaps that'd be the way to go.
by Kabacaru 14y ago
Because it's harder to set the content-type from browsers.
Perhaps if your API won't be that useful to browser based clients, perhaps that'd be the way to go.
- masklinn 13y ago> Because it's harder to set the content-type from browsers. That's only when using HTML forms or links, TFA does not even mention the option of multiple representation of resources so it's irrelevant: there's nothing hard to adding an Accept header to an XHR.
- mnarayan01 13y agoI assume he's talking about developer discovery/exploration.