Open solaris007 opened 7 months ago
@iuliag @ekremney @dzehnder @AndreiAlexandruParaschiv @alinarublea please review / provide input
For my understanding: the url is a page URL that has nothing to do with the sites we have in StarCatalogue?
The Location header in the post response could contain the url to poll for the status of the task.
The current status of the job ('pending', 'in_progress', 'completed', 'failed').
If the possible status values are known, we should use an enum.
What's the difference between 'pending' and 'in_progress'?
When is the task completed
, after all the subtasks are completed? Would you show partial results as the subtask complete, or just final results?
It would be good to have an example of the response body for failed
as well.
Generally, I think you'd have a different schema for the response body depending on status (or state), with different required properties.
For 429, it should include the Retry-After
header.
In order to integrate the PoC-style Content Scraper and Content Processor an HTTP API is needed providing the following features:
Here is a proposal for amending the HTTP API spec: