Thomas Kluyver

One line per input may be annoying if you have any multi-line inputs (loops, function definitions, etc.). Of course, it's easy enough to get round that either with some delimiter...

There's no need for it to be a magic in IRkernel, though - it would work just as well as a regular function `connect_info()`.

Which docs? If it's on the Jupyter side, we may need to clarify that that's something specific to IPython. The docs haven't all been updated since the big split.

Thanks, opened jupyter/notebook#1504 for it.

I see you implemented 2 in 74f7e7115e7fba210bb8cae02e23a1ad8acbe7ff and 1c357fdcf9a510d320fa495d8681ca300f2950e2 . We appear to be somewhat ambiguous about whether a `text/plain` format is required. The messaging docs say it should always...

True, but `display_data` and `execute_result` are mostly equivalent. I don't remember any discussion that text/plain is necessary for execute_result but not for display_data. Configuring lists of things is always technically...

BTW, I realised this while writing a minimal example of a proxied application to check that I knew what was going on: [hello_jupyter_proxy](https://github.com/takluyver/hello_jupyter_proxy).

> A unix socket only works if the proxied application will use it (in general they won't). I realise I missed some context: I am looking at writing small applications...

Thanks! Yes, I'm particularly interested in what can be done without special privileges - I don't have sudo access to our cluster. :slightly_smiling_face: In terms of the config, the least...

I spent a little while looking into what this would take, and I think it should be fairly doable. The trickiest piece looks like the websocket support - tornado's `WebSocketClientConnection`...