[IPython-dev] Message spec draft more fleshed out
Wed Aug 11 16:50:25 CDT 2010
On Wed, Aug 11, 2010 at 12:14 PM, MinRK <email@example.com> wrote:
> A note on the heartbeat section.
> I don't know if you guys are using the heartbeat messages, but my heartbeat
> monitor doesn't use Python messages at all. It's pure ZMQ, so it never
> enters Python code, and packing up of reply messages isn't available. The
> monitor sends out a single zmq message (right now, it is a str of the
> monitor's lifetime in seconds), and gets the same message right back,
> prefixed with the zmq identity of the XREQ socket in the heartbeat process.
> This can be a uuid, or even a full message, but I don't see a need for
> packing up a message when the sender and receiver are the exact same Python
Very good points. I think we should just copy this description into the
> The model is this:
> monitor.send(str(self.lifetime)) # '1.2345678910'
> and the monitor receives some number of messages of the form:
> ['uuid-abcd-dead-beef', '1.2345678910']
> where the first part is the zmq.IDENTITY of the heart's XREQ on the engine,
> and the rest is the message sent by the monitor. No Python code ever has
> any access to the message between the monitor's send, and the monitor's
> On Wed, Aug 11, 2010 at 00:39, Fernando Perez <firstname.lastname@example.org>wrote:
>> On Tue, Aug 10, 2010 at 1:02 AM, Fernando Perez <email@example.com>
>> > Hi folks,
>> > here:
>> > is a more fleshed out message spec document for feedback. I'd
>> > especially like to hear from Omar and Gerardo if you notice any
>> > important point missing, since you've been thinking a fair bit about
>> > this.
>> Thanks a lot for the feedback so far. It took a lot more work than
>> I'd thought, but I think we now have a fairly solid first pass at a
>> *complete* design and messaging spec (excluding the parallel computing
>> part). Here's the last version I just put up:
>> but if you prefer to read civilized HTML I built and pushed the nightlies:
>> At this point, please do pound on this document. This should be our
>> *real* spec, the actual code should match it, and it should be
>> complete. We'll be implementing off of this, so anything that I've
>> missed, please do point it out.
>> Thanks for any feedback!
>> IPython-dev mailing list
> IPython-dev mailing list
Brian E. Granger, Ph.D.
Assistant Professor of Physics
Cal Poly State University, San Luis Obispo
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-dev