[IPython-dev] Generic design for an IPython servers that talks to editors (TextMate, vi, emacs)
Sun Dec 7 15:56:35 CST 2008
On Sun, Dec 7, 2008 at 9:52 AM, Brian Granger <firstname.lastname@example.org> wrote:
>> Please forgive my Twisted newbie-ness, but why not use an
>> IProcessProtocol? I realize that running a service on a socket lets
>> multiple editors connect, but is that really a likely use case?
> I think potentially yes. But remember, you can't connect/reconnect a
> process protocol. Also, I don't think you can attach a process
> protocol to a process that someone else started. Using a Unix socket
> makes all of these things trivial.
I see. Not being able to reconnect is obviously a deal breaker. Thanks
for the explanation.
>> you're really planning on having multiple clients, don't you have to
>> end up replicating (or using) all of IPython.kernel to deal with the
>> semantics of multiple clients connecting to an IPython instance?
> No, not really, because the only capability we are exposing is
> execute, and we don't even return stdout (it is printed in IPython
> itself). But, yes, eventually, all of this should be based on the
> engine itself. But for now, this is an easy thing to maintain. Have
> a look at the code and you will see what I mean.
I see what you mean. It is very clear code, so it's definitely worth
going with this approach. Thanks for bearing with my nagging.
> Good question though.
>>> IPython-dev mailing list
More information about the IPython-dev