On Tue, Feb 28, 2012 at 02:37:49PM -0800, marsbomber wrote: > > Nicola, hope this helps you in some ways. Unfortunately what I'm > building is close sourced, I cannot disclose > anymore details.
Hello Mars, can you tell us for which domain you developed your solution? > As something for myself, John, does what I describe make sense to you > at all? Am I over-complicating things? > Or there are aspects from Ruote, which I simply missed, that could > simplify things a little? This "RabbitMQ between ruote and the hard-working participants" pattern seems to be used by lots of people. I sometimes wonder if a simpler queue, like a Redis queue wouldn't be sufficient, but I guess people are used to deploy and manage RabbitMQ and they like to have fancy topologies so it makes a lot of sense. I also wonder if a 0mq setting might not be nice. We could also use 0mq inside of a ruote storage (might be very fun). I have to say I'm impressed, we first talked 39 days ago (according to my Twitter client) and since, you built such a nice system, barely asking any questions. BTW, we should discuss if your deep-merge is a good candidate for the master branch. Keep up the great work! -- John Mettraux - http://lambda.io/processi -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
