[Swift-devel] iPython parallel coasters

[Mihael Hategan]

I was exploring AMQP as an alternative to writing my own protocol (which
turned out to be coasters) somewhere before I started working on Swift.
In spirit, it seemed to do exactly what I wanted. Unfortunately, there
were no reasonable implementations at the time, which I see has changed.

So I do think this is worth exploring although I'm not quite sure about
the moving parts part. The outsides of things can be deceiving.

Mihael

On Thu, 2014-05-29 at 10:47 -0500, Michael Wilde wrote:
> [Moving this part of the discussion to a new thread.]
> 
> Seems like less moving parts than coasters: it would all be in Python 
> (instead of Java + Perl); would have iPython community support; and 
> would be based on a standard protocol (ZeroMQ implementation of AMQP).
> 
> iPython parallel has almost the exact same process architecture as Swift 
> Coasters.
> 
> Seemed worth exploring.
> 
> - Mike
> 
> On 5/29/14, 10:28 AM, Tim Armstrong wrote:
> > ...
> >
> > What's the motivation for the IPython idea? It feels like a lot of moving
> > parts to me.
> >
> > - TIm
> >
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel