Seems like that would be an anti-corruption layer, i.e. that would shield your application services from inter-component communication implementation details. So, not useless "in theory". As for boilerplate... can't say anything really, but that should be solvable in some way. Like using dynproxy to autogenerate consumers which will call into your app services. That's entirely possible if you have a suitable naming convention for consumers/services.
On Tue, Apr 14, 2009 at 11:35 PM, rg <[email protected]> wrote: > > Now I can write as many single-message > consumers as it's needed by RSB, but this is just writing tons of > useless boilerplate code - how little reason is that? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
