FYI - I just cut a release of clj-refactor.el and refactor-nrepl https://github.com/clojure-emacs/clj-refactor.el/blob/master/CHANGELOG.md#240-2018-08-26

No changes since the last 2.4 snapshots.

I have a couple questions about nrepl.server, which I am embedding into my server-side app. 1) Is there a way to configure the initial namespace a client will be placed into (from the server?) 2) Is there a way to get notified when a nrepl client connects/disconnects? (e.g. some kind of hook?) It would be good for logging, etc.

> 1) Is there a way to configure the initial namespace a client will be placed into (from the server?)

Currently no. You can just do some eval changing the ns after starting the server.

That’s something we can probably add.

> 2) Is there a way to get notified when a nrepl client connects/disconnects? (e.g. some kind of hook?) It would be good for logging, etc.

Don’t think so. But it’d be easy to add something like this.

@bozhidar WRT notifications, is that something that could be done via middleware, or would need to be part of nrepl.server proper? For both "features", I feel they would be very helpful for embedded nrepl.server uses. When building a nrepl server into a app, one might well want to have a namespace prepared with easy access to the vars (eg the "system" var for component) and functions that would be helpful for maintenance, control, and status of the app in production. And it would be great to be able to log/monitor/alert on nrepl-client connections...

I'm not at all handy with elisp, but since this is Clojure, I have a fighting chance. Should I tale a look/stab at these? (in my non-copious free time 😞 )

> @bozhidar WRT notifications, is that something that could be done via middleware, or would need to be part of nrepl.server proper?

nREPL itself.

That’s one potential approach for a generic notification mechanism.

https://github.com/clojure-emacs/cider-nrepl/blob/master/src/cider/nrepl/middleware/util/nrepl.clj#L14

(at least in broad strokes)

Right now all the messages you’d get from the server are the result of some request you sent to the server.

Connecting and disconnecting clients is transport specific. Eg not supported by http

True.

I guess in such cases we simply won’t fire any notifications. There should probably also be some mechanism to subscribe a session to such notifications, or alternatively they can be broadcast to all sessions.