mesh-based message queueing

[stewartoallen]

No description provided.

[abramsm]

minor: can we use log.error vs e.printStackTrace?

in general this looks good to me. We'll need to run it through our test stack before merging into master.

[stewartoallen]

of course. thanks.

On Mar 25, 2014, at 5:49 PM, Matt Abrams notifications@github.com wrote:

minor: can we use log.error vs e.printStackTrace?

in general this looks good to me. We'll need to run it through our test stack before merging into master.

—
Reply to this email directly or view it on GitHub.

[tea-dragon]

Looks fine to me. I would rather be able to encapsulate the large if (system.property) blocks into implementation classes, but oh well. I tried resolving the merge conflicts a couple times but my merge skills are imperfect and i'm not entirely familiar with the code that has conflicts so I am giving up on doing that myself for now.

[tea-dragon]

closing since the other PR is supposed to supercede this one.