[IPython-dev] Two frontends, one kernel
Doug Blank
doug.blank at gmail.com
Sat May 3 00:11:54 EDT 2014
Got this stage working; it was largely just getting that identity on the
front of the shell ROUTER packets. I suspect that there will be things to
expand and refine once we can start using the kernel as an engine in a
cluster... I hope that using 3rd-party kernels in a parallel cluster is
still on the TODO list.
I'd be glad to look over any new docs. Thanks again!
-Doug
> Adding an example request/iopub/reply cycle in the wire format is a good
> idea. I will try to draft one this weekend. The general principal: one
> request has one reply. the routing identity is relevant only to that one
> reply, and the reply's routing prefix should be identical to the request's.
> Side effect messages on IOPub do not use routing identities. But they do
> have a slightly analogous behavior called a subscription topic. This value
> should not be influenced by the routing prefix, and in practice has no
> effect because frontends subscribe to all topics (this last statement is
> already in the msg spec doc).
>
> -MinRK
>
>
> Thanks so much... I feel I am getting close!
>
> -Doug
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20140503/81234731/attachment.html>
More information about the IPython-dev
mailing list