Fix data aliasing issues

[djmitche]

This categorically addresses the unintended sharing of data structures between cluster components; #198 is one example of this issue.

Note that this makes a fresh copy of the message for each destination, avoiding aliasing either between the source and destination, or between multiple destinations.

This requires a little trickiness in Python: since we use message in a closure, we need a distinct variable for each destination, and we need to make that copy during the send invocation, not when the timer expires.

[MichaelDiBernardo]

Cool, thank you @djmitche! I'll check up before publication to make sure that these code changes propagate to anyplace they may be in the chapter.

[djmitche]

Awesome, thanks!

On Sun, Mar 6, 2016 at 10:01 AM, Michael DiBernardo <
notifications@github.com> wrote:

Cool, thank you @djmitche https://github.com/djmitche! I'll check up
before publication to make sure that these code changes propagate to
anyplace they may be in the chapter.

—
Reply to this email directly or view it on GitHub
#200 (comment).