Tom, Sharp eyes. :-) I should have left IRedundantService out of it -- that's just a detail of our implementation.
Our client-side code looks for primary=true if IFooService is an IRedundantService and doesn't look for that Entry if not. This has allowed us to change our mind about whether a service should be a pool of equals or a primary-backup hierarchy without changing client-side code. I'm glossing over a ton of the details (like that the primary=true filtering happens client-side instead of in the registrar), but I think you can see what I mean. Chris -----Original Message----- From: Tom Hobbs [mailto:[email protected]] Sent: Tuesday, February 16, 2010 10:42 AM To: [email protected] Subject: Re: Service Wrapper Example Hi Chris, <snip> What is the purpose of "IRedundantService". Surely "IFooService" could just join the groups of all the other "IFooService" services? Interesting none the less though. Thanks for sharing. Tom
