On Tue, 2011-03-08 at 09:53 -0700, Clark, Joel wrote: Hey Clark Joel,
> > There are real-world scenarios (think mirroring sensitive enterprise or > > social web data) were an additional address book is needed, because data > > must not be mixed with the "normal" contacts. > > And systems that have multiple user profiles Preferably you use a Tracker per UNIX user. But also here can graphs be used if necessary. I think EDS is similar in this regard. We don't support system-wide Tracker instances; we lack a use-case for that (and it sounds like a silly idea to us too). > > You mentioned plans to add access control. Can that be implemented while > retaining the direct read capability and the > > Also essential for systems with multiple user profiles and concurrent > multi-user access. So as mentioned in earlier reply to Ohly Patrick, is user access to meta.db regulated using UNIX file permissions using the GID::metadata-users credential (which grants your process group-id permissions). When this read access isn't available then libtracker-sparql falls back to FD passing over D-Bus automatically. Unfortunately needs WAL also writable access to meta.db's directory (for the journal files that it writes) but said GID:: credential should only be granted to certified applications (if such security is of importance for the integrator). Cheers, Philip -- Philip Van Hoof freelance software developer Codeminded BVBA - http://codeminded.be _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
