4 ms·
> REST style routing interface I'm fairly certain there is no such thing, and parsing parameters out of the URL path has nothing to do with REST either.
by cname 11y ago
> REST style routing interface
I'm fairly certain there is no such thing, and parsing parameters out of the URL path has nothing to do with REST either.
- paulddraper 11y agoSort of. URL "routing" is necessary for REST, as opposed to an RPC (or GraphQL) style POST to a single URL. But yes, other than arbitrary URL routing existing, there is nothing that makes it have a "REST" style.
- cname 11y agoREST only requires uniquely-identified resources. There's nothing in that stopping you from having a single endpoint that takes query parameters to identify those resources.
- paulddraper 11y agoYes, but that doesn't invalidate what I said. It still counts as "routing" on the request URI. (Instead of, say, routing to application logic primarily based on a header or the entity like GraphQL). There's zero difference between path and query string, other than one is meant to be hierarchial and the other is not.