> It looks like you are hoping that the agency server will be something > to assist clustering at a later date. Is that true? (if so, I will have to > wipe the drool from the corner of my mouth). If so, we need to have a plan
Yeah I'm drooling too. Berin you clarified many things in your email. I want to try to see if I can summarize some things as I understand them and perhaps add to it: 1. Use a registry to centralize configuration information - ADDITION: if asynchronous notifications are enabled then component reconfiguration is possible. 2. Use an interface to the registry that is location transparent. The information can come from a local configuration (Java prefs, the NT registry, or xml file etc) or from a remote a database or an LDAP server you don't care. JNDI is the most plyable of interfaces for that endeavor and has several of the providers you're looking for. 2. JAR dependency resolution is handled by using the registry information and the repository. This is like maven repo concept but is smarter in that it leverages registry information. If maven POMs were stored in a registry you would have the same level of behavior. In fact the functionality can be added to the common's discovery facility and used for both Maven and Merlin's repo. 3. Use the registry to manage cluster configurations and as a dynamic component or service lookup like a cross between an ORB and a UDDI registery. What services are out there? Where are they? How can I talk to them and what are their interfaces? These are the questions answered by the registry as well right? Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
