Allow to remove max request response size

[MateoLostanlen]

#190 introduce a response size limitation of 50, I get the point of doing this but can we add an optional prams to drop this limitation if we need it ?

[frgfm]

Hey there :wave:

I thought about it and here is what went through my head:

• the goal here is to paginate the response similarly to most popular REST APIs on the planet: say you have 1000 elements in the response with pages of 100 elements, that's 10 pages. By default, it only returns the first one, and we can easily make it so that you can request other pages.
• however, I don't think we should allow request for the entire thing

The reason behind that is simply to avoid cluttering the RAM of the server and have it crash. Would that be OK? (to be able to select the page you want to request, and then you'll aggregate on your own?)

If you have another idea, I'm honestly all ears :)

[MateoLostanlen]

Hi, there,

Yes, this page system is fine for me, I just need the metadata to exploit the collected images :)

[frgfm]

Closed by #412 :)

• the fetching of sequences for a given date is paginated so you have control over this
• fetching the last unlabeled sequences gives at most 15 sequences within the last 24 hours
• fetching the detections of a given sequence gives the last 10 detections