On Wed, 2009-07-29 at 09:03 +1200, Angus Salkeld wrote: > Why do you need this? > > I know the config file is set out like this, but why force the requirement > onto objdb? > We could always change the config file to remove this requirement, but I wonder about the case of something like using this for checkpoint service internally.
For example, create a checkpoint with two sections. The checkpoint is an object, the two sections are an object. How do you read the various sections? Regards -steve > -Angus > > On Wed, Jul 29, 2009 at 8:07 AM, Fabio M. Di Nitto<[email protected]> > wrote: > > On Wed, 2009-07-29 at 07:30 +1200, Angus Salkeld wrote: > >> Hi > >> > >> Here is a first attempt at an easier to use API for objdb. > > > >> 2) Each object/key must have a unique name (as a string) > >> 2.1) So no child objects named the same (service, logging,...) > > > > This breaks current requirements from the objdb as we need to have > > objects in the same level with the same string name. > > > > Fabio > > > > > _______________________________________________ > Openais mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/openais _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
