Tim,
Your middleware never sends a response. Each request message can produce
multiple response messages, sent at some later time (i.e. the request/response
cycle is fundamentally asynchronous). Handler return values are ignored.
So, assoc'ing the "result" into the request message as the retu
It looks like your connection is broken somehow, this might be caused by an
OS level issue(firewall etc.) but not the application itself. To test if
this is due to an OS level issue, I suggest you to try connect nREPL by
telnet, here's how to start nREPL in a TTY mode, in any REPL session type