On Wed, Apr 21, 2010 at 02:50:40AM -0700, avishai wrote: > > Well, I think it would be better to focus on controlling dispatch > locality in the broader sense then implementing something that is host > specific. After all, you may want to have the dispatch select the host > by fields other than hostname.
Sorry, this was just an example. > Perhaps a selection criteria - a boolean ruby block - would be better? > and perhaps while we're at it, maybe it's better to just add a general > dispatch hook and leave room for crazy ideas... It's just ruby code, it's easy to re-open a class. It's not forbidden either to provide your own implementation of the ruote services. http://github.com/jmettraux/ruote/blob/ruote2.1/lib/ruote/context.rb#L138-156 On the other hand, you could place your routing logic in your participant implementation, shared by all workers. The participant knows where the "real" participant is. Plenty of room for crazy ideas. Best regards, -- John Mettraux - http://jmettraux.wordpress.com -- 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
