Corey, I don't want to discuss opinions, this problem is a big issue for me and I'd rather talk about solutions. I have a real system with real components that exchange messages. These components provide application services, and message exchange is only an internal implementation detail. So they are message consumers and message publishers, but it's not their function, only a means of inter- component communication. That's why I don't think message consumer shouldn't do anything else. 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 -~----------~----~----~----~------~----~------~--~---
