Spec support for connection close notification
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- clojure
- Domain
- backend-api-design
Research direction
Start with the Ring specification and the issue’s examples of http-kit’s AsyncChannel and Aleph’s manifold streams. Compare how those systems expose connection closure and determine what a portable Ring-level mechanism would need to define. Done means reaching agreement on a proposed standard behavior and documenting its scope.
Written by the indexing model from the issue text.
Description
The Ring spec provides no mechanism for applications to be notified when a client connection is closed. This limitation is particularly relevant for long-lived streaming responses (e.g., Server-Sent Events), where the server may wish to release resources as soon as the client disconnects.
Currently the only way for the streaming server to discover the connection has been closed is to attempt a write to the output stream and catch the failure.
Some servers, such as http-kit (via its AsyncChannel) and Aleph (via manifold streams), already offer this functionality.
This issue is to open a discussion on whether and how the Ring spec could define a standard way for applications to observe the connection closure event.
- Dominant language
- Clojure
- Stars
- 3.9k
- Forks
- 528
- PR merge metrics
- No merged PRs in 30d
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.
More from ring-clojure/ring
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
ring-clojure/ring#546 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
ring-clojure/ring#544 · 3 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ring-clojure/ring#541 · 3 comments ·
-
[ring-jetty-adapter] No control over exceptions thrown when obtaining item from ISeq response body Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ring-clojure/ring#531 · 4 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
ring-clojure/ring#530 · 3 comments ·
All issues in ring-clojure/ring
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
.Team/Metabot Priority:P3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
scalar-labs/scalar-jepsen#222 · 1 comment ·