opengeospatial / opengeospatial/ogcapi-processes
Default execution mode should be asynchronous.
Open
Nobody has claimed this yet.
Part 4 (Job Management)
- Dominant language
- AsciiDoc
- Stars
- 63
- Forks
- 46
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
Requirements 26 item C says: "The server SHALL respond synchronously if, according to the job control options in the process description, the process can be executed in either mode."
I think this is the UNSAFE play. We should change this to ASYNCHRONOUS by default.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Requirements 26 item C in the process description and the 36-comment discussion on this issue. Determine whether the default execution mode should change from synchronous to asynchronous, then update the requirement and any affected explanatory text once the specification decision is settled.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100