Carsten, I am not sure I fully understand the scope and usage of this API. From what I have seen in the code and the mailing list discussions, it is meant to expose clustered Sling instances to each other and send notifications when instances are added and removed. It also facilitates the selection of a leader instance and provides the ability to interchange properties.
Is this all correct? If so, what is the intended use? Will this be used to directly transmit information through properties or will the properties be used to exchange connection information? Thanks and my apologies for my ignorance. Thanks, Dan -----Original Message----- From: Carsten Ziegeler [mailto:[email protected]] Sent: Friday, May 17, 2013 3:33 AM To: [email protected] Subject: Releasing discovery Hi, I'm planning to cut a release of the discovery modules next week, this includes: api support - a general useful property provider service (formerly in the api package) standalone - a standalone implementation of the discovery (formerly in the api package) impl - the full fledged repository based implementation If you see any issues with releasing this stuff, please speak up now. I guess the most important part is the API as we have to support this :) Thanks Carsten -- Carsten Ziegeler [email protected] ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3336 / Virus Database: 3162/6325 - Release Date: 05/15/13
