David Teigland wrote: > On Wed, Mar 26, 2008 at 12:24:23PM -0700, Steven Dake wrote: >> This diagram indicates there is a need for two separate levels of >> datahiding. The first level is the libcsdb (corosync db) which then >> some other library parses for information specific to the cluster stack. >> Then this other api is used. In my mind this type of double abstraction >> serves no purpose. They both serve up the same data. It also may > > Right, libcsdb isn't doing anything, scratch it out. I just added it > because Chrissie suggested another lib in there might help.
The main reason for the double library was to avoid linking libxml with an openais component. While I'm clear (and heartly agree) that large external libraries should not be part of the exec I had a bit of a hard time getting a clear policy for IPC-based libraries. I'm not wedded to either solution, I was largely hedging my bets. >> Caching these values is not suitable in my opinion. Just use the rest >> of the infrastructure we already have in place to parse them and put >> them in the objdb and make them available via some unnamed api. > > Fine, scratch that too, it's not important. > I'm not going to push this either way at the moment, but I think we should keep in available as an option. It might be helpful as an emergency fallback to get a cluster up where there is no other way of getting configuration information. -- Chrissie _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
