On Do, 2010-02-11 at 17:19 +0000, Lukas Zeller wrote: > On Feb 11, 2010, at 13:44 , Patrick Ohly wrote: > >> b) An enhanced SelectProfile() in binfileimplclient.cpp, which would > >> check that flag and figure out which superdatastore to instantiate in > >> addition to the normal datastores. > > > > Is that really necessary? If we require that all relevant targets are > > enabled, both for the <superdatastore> and its underlying <datastore>s, > > then SelectProfile() can simply instantiate them all. > > There can't be a a "target" nor a TBinfileImplDS for the superdatastore.
You almost had me convinced and I already changed quite a bit of code, until I came to the point where I wanted to call dsSetClientSyncParams() for the superdatastore. If that store has no target associated with it, how can the client set the URI? The only solution I see is to make the subdatastore URI's more complex: instead of <foo>, let's use <foo:uri> where "foo" is the name of the superdatastore and "uri" its remote URI. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
