[Meego-architecture] [MeeGo-dev] Some architecture changes (MSSF / Buteo / PIM storage)
Philip Van Hoof
philip at codeminded.be
Tue Mar 8 02:31:09 PST 2011
Interesting thread ... (not).
Congratulations for guiding it with insightful and non-emotional
Can somebody from Intel answer One of the questions about EDS?
On Mon, 2011-03-07 at 22:40 +0100, Philip Van Hoof wrote:
> Can you explain us, how does EDS improve privacy control compared to
> Tracker's RDF store? Does EDS have a way to represent different graphs
> (part of Tracker's future plans to do per-resource privacy control)?
> How in EDS do you say that data (about) x isn't to be made
> available to queries made by application y? It's the first time
> that I hear that EDS has such a privacy related capabilities.
> Can you also go a bit deeper into how EDS's performance compares to
> Tracker's RDF store for comparable data entry operations? Have you guys
> done measurements on this? Can the results of these measurements and the
> method to reproduce be publicized? Are the queries you used available
> somewhere? Where?
> What do you mean with scalability? Scalable over multiple application
> domains other than PIM? Or scalable to more data?
> And what kind of data? I wonder how EDS is or can be more scalable
> when the underlying database technology (SQLite, apparently) is identical.
> In Tracker is each class stored in a decomposed table. This means that
> contact and E-mail data are each in separate tables. Although decomposed
> typically makes INSERT a bit slower, SELECT is a lot faster.
> How will or does EDS make SELECT equally 'scalable' with equally complex
> Also note that the Tracker team optimizes both INSERT and SELECT
> use-cases on a use-case per use-case basis, using its domainindexes and
> Have you contacted the Tracker team about the scalability
> problems (if any)?
Philip Van Hoof
freelance software developer
Codeminded BVBA - http://codeminded.be
More information about the MeeGo-architecture