Map HTTP sessions to nREPL sessions
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 192
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Currently HTTP sessions and nREPL sessions are completely independent. HTTP sessions only matter insofar as they retain the message queue for responses from asynchronous or long-running operations.
It would be useful to optionally map HTTP sessions onto nREPL sessions, so that a client's session state persists naturally across HTTP requests.
Additionally, supporting nontextual REPL interactions over HTTP has not been addressed.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by tracing how HTTP sessions retain response queues and how nREPL sessions hold client state; define the optional mapping and nontextual interaction requirements before implementing. Done means HTTP requests can preserve nREPL session state when enabled and nontextual interactions are supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100