What problem is this feature trying to solve?
I'm archiving my collection (manifest-only). After ~110 requests the server begins rate-limiting connections for roughly an hour. I suspect the limit is triggered by logging in for each request.
How would you like it to be solved?
I'm wondering if the ability to make multiple/many manifest requests to the same depot within a single login session would bypass this limit?
Have you considered any alternative solutions
The only solution I have at this point is automating it while respecting the rate limit, but I'm still waiting an inordinate amount of time for the software with 5k+ manifests per depot.
Additional Information
No response
What problem is this feature trying to solve?
I'm archiving my collection (manifest-only). After ~110 requests the server begins rate-limiting connections for roughly an hour. I suspect the limit is triggered by logging in for each request.
How would you like it to be solved?
I'm wondering if the ability to make multiple/many manifest requests to the same depot within a single login session would bypass this limit?
Have you considered any alternative solutions
The only solution I have at this point is automating it while respecting the rate limit, but I'm still waiting an inordinate amount of time for the software with 5k+ manifests per depot.
Additional Information
No response