As an API user, I want to handle long-running queries that take >10 seconds. about registry-api-service

[al-niessner]

Is it not the responsibility of the client to do the timeout? cURL has a timeout flag that will stop the transfer after the timeout independent of what or where cURL is in the request. Other download tools like wget also have the timeout.

Putting the timeouts in the server makes it awkward on the user. If I want a page of 500 items and I have all day, then I expect to start the cURL and wait for it to finish even if it takes the whole day. If the server times out at 10 seconds, then how do I know how long it will take since intermediate information is lost? Do I try 30 seconds only to have it fail, then 60 seconds, then 120 seconds, etc until it finally works? That will be super annoying.

However, if I know I only have 10 seconds before I need the answer then I can set the timeout at the client to give up and then do something else. Or maybe I only have a minute or two.

[tloubrieu-jpl]

Issue moved to NASA-PDS/registry-api #15 via ZenHub