4 ms·
REST only requires uniquely-identified resources. There's nothing in that stopping you from having a single endpoint that takes query parameters to identify tho
by cname 11y ago
REST 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.