Document caveats around key-value pinset stores #97
Labels
dif/expert
Extensive knowledge (implications, ramifications) required
effort/hours
Estimated to take one or several hours
need/analysis
Needs further analysis before proceeding
need/community-input
Needs input from the wider community
P2
Medium: Good to have, but can wait until someone steps up
topic/devexp
Developer experience related things
topic/docs
Improvements or additions to documentation
Extracted from ipfs-shipyard/pinning-service-compliance#118 (comment):
I'd like to at the very least update the Pagination and filtering section to loosen up requirements and provide some rules of thumb for service implementations backed by key-value stores.
@hsanjuan @SgtPooki
What is the current behavior of ipfs-cluster around
GET /pins
, filtering and pagination?What would be the best compromise we should document?
Some ideas how to handle "sorting and filtering becomes too expensive" scenarios:
GET /pins
always returns405 Method Not Allowed
before
andafter
filters (they produce405 Method Not Allowed
),GET /pins
returns pins in random orderAre there better ways?
The text was updated successfully, but these errors were encountered: