2 ms·
In most contexts what you actually need is REST as in "JSON RPC over HTTP" instead of REST as Roy Fielding intended. So the recommendations in the article are
by PeterisP 9y ago
In most contexts what you actually need is REST as in "JSON RPC over HTTP" instead of REST as Roy Fielding intended.
So the recommendations in the article are actually valid and useful, but we'd need to come up with another name to properly distinguish which "REST" we're talking about, at least unless/until one of these usages fades into obscurity.
- dozzie 9y ago> we'd need to come up with another name to properly distinguish which "REST" we're talking about "Underspecified, broken half-implementation of RPC" is quite precise, but most of the programmers don't like being reminded that they implement a brain-dead idea. I never understood why people don't use one of the already-defined RPC protocols, rolling instead their own versions (each different) that don't even signal errors properly.