Map HTTP sessions to nREPL sessions #49
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.