non compliant paging

[matthewhanson]

sat-search uses the parameters page and limit when the number of Items is more than limit.

This is not compliant with STAC because STAC doesn't specify a mechanism to do paging. The assumption is that all results will be returned, although this may cause errors in some implementations, such as sat-api (see #69 ).

See the STAC issue discussing this:
radiantearth/stac-spec#381

One possible solution is to remove paging and instead use the next links. However, next links unless combined with caching and session tokens, can fail if combined with lengthy POST rather than GET requests.

If paging remains implementation specific then it will be difficult to make sat-search generalized enough to work with all implementations when the number of items searched for is larger than the max response size for the given implementation.

cc @vincentsarago @sharkinsspatial @m-mohr @cholmes

[m-mohr]

If it's not clear from context whether to send GET or POST, would it be an option to add a method attribute (defaulting to "GET") to the links? That could be interesting anyway also for other (rare) use cases.

[matthewhanson]

But how do you provide a next link when it was a POST request? It won't have the body in the link, and if you convert the body to GET parameters it could cause a problem in some cases.

You'd have to cache the request and return a token that would be used to get to the next page, which is a bit non-trivial (especially for a serverless app). It seems easier to have a page parameter and make the client explicitly page when needed.

[m-mohr]

I must admit, that was not the best idea I had yesterday night. I thought about tokens, but forgot that in this case I don't need to send it via POST anyway. I guess the better place to discuss it is here: radiantearth/stac-spec#381 We probably should make a pro/cons list on every possibility (cursors/offset(pages)/next links/...) and then decide for one of them. I guess each of them has a big con though.

(It always blows my mind when POST is used for things that GET should be used for.)

[matthewhanson]

The about-to-be-released version of STAC (0.7.0) now has page as a parameter, so this is now moot.