Commitments to requests
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
There are use cases [citation needed] that require servers to process requests where servers may not want to commit to providing a response before closing the connection.
For example: creating or deleting /foo/bar/baz has both idempotent and non-idempotent side effects. Server that are capable of making decisions based on side effects may want to respond quickly to inform clients about their request.
One way to effectively communicated that is in a response with 202 status.
What level of conformance should be expected of servers and clients to handle 202?
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 the request-handling use cases described in the issue and determining the expected server and client behavior for 202 responses. Done means the specification records an agreed conformance level for both servers and clients; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100