[IPython-dev] api between kernel, web server and frontend

[Brian Granger]

On Thu, May 13, 2010 at 3:00 PM, Fernando Perez <fperez.net at gmail.com> wrote:
> On Thu, May 13, 2010 at 2:25 PM, Brian Granger <ellisonbg at gmail.com> wrote:
>>
>> While IPython will always ship with a non-OMQ version, for things like
>> you are talking about, I don't see 0MQ as optional.  I simple don't
>> think there is another good transport layer (at least not one that is
>> pure python and more lightweight that 0MQ).
>
> Just to add context, I think Ondrej's view (at least that was my view
> when we worked on this) is that there could be non-0mq clients, such
> as a web-based one, accessing an ipython kernel, and that what we
> should agree on is the protocol description.

By protocol description, do you mean the precise format of the JSON messages?

> For *ipython itself*,
> we're 100% committed to doing all communications over zmq, and for now
> we don't have the time to write the http server wrapper around a
> kernel, but if that were to exist, then others could connect to the
> kernel over http.
>
> I'm going to spend a bit of time now moving these docs over to ipython
> itself, so we have a place to start putting down the protocol
> description.

OK, I think this makes sense.

Cheers,

Brian

> Cheers,
>
> f
>



-- 
Brian E. Granger, Ph.D.
Assistant Professor of Physics
Cal Poly State University, San Luis Obispo
bgranger at calpoly.edu
ellisonbg at gmail.com