'Right way to express a range query in the kv storage via REST API?
Imagine a simple kv store, that supports a range queries and uses integers as a keys.
GET /kv/:key
PUT /kv/:key (payload is the value)
DELETE /kv/:key
I'm thinking about /kv/?from=1&to=100 but the idea of required query parameters is kinda ugly. What would be the right way to represent a range query via REST in a kv store?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|