Chas Emerick

Isn't this better covered by #41? The `:repl-url` should always contain the correct URL, even given customized hostname, port number, session ID, etc…

Yup, you're right. This is being caused by some kind of buffering, either in piggieback, or in Austin's "constrained order" evaluation mechanism (which I don't fully understand, was inherited from...

Not off the top of my head, no. FWIW, Austin will stop using `clojure.browser.repl` with #50, which may (should?) eliminate any side effects of its implementation.

Right, that's caused by [this](https://github.com/clojure/clojurescript/blob/master/src/cljs/clojure/browser/repl.cljs#L31) (catching `js/Error`). Austin will be getting its own client-side implementation in #50, which will fix this. In the meantime, a fix (or ticket, anyway) for...

Either way, there's a server, something needs to be available to compile the ClojureScript you're evaluating, etc. Given that, what's the benefit of a websocket server vs. HTTP? Note that...

There are a couple of things: 1. LightTable's approach works because WebSockets are not bound by the same-origin policy. We can modify Austin's embedded server to add the necessary `Access-Control-Allow-Origin:...

An easier approach would be to allow the user to "mount" a local directory as the root of all resources served for a particular REPL session (mock usage here): ```...

Yes, it looks like the approach I described is exactly what was implemented there. So, "borrow", yes, conceptually. The user in question hasn't submitted a PR themselves, so any kind...

The failure is that the `:print` dispatch for `handle-post` is attempting to `read` the content that was printed; this is yielding some value that `print` on the Clojure side is...

I don't currently use ritz (or emacs, which is where `nrepl-ritz-jack-in` comes from), so I can't test this immediately, but will return to it soon.