On Mo, 2011-03-14 at 19:03 +0000, Philip Van Hoof wrote:
> On Mon, 2011-03-07 at 08:09 -0800, Arjan van de Ven wrote:
>
> Hi Arjan,
>
> > PIM storage
> > ===========
> > The Address book, Calendar data and Email are currently stored in a
> > tracker database, and accessed (officially) via a QtMobility API set.
> > There are a range of issues with this implementation, starting with the
> > complexity of adding privacy controls, the performance and
> > scalability as well as the completeness for doing a proper syncml sync.
>
>
> http://mail.gnome.org/archives/tracker-list/2011-March/msg00033.html
Okay, I bite.
The comparison is favoring Tracker in a number of ways:
* Having the Evolution UI running while inserting contacts into
EDS slows down the whole process because all data is also
getting sent back to the UI. This is more complex than just
inserting the data into Tracker, which has nothing reading that
data during that time.
* You use the low-level Tracker API to create contacts in Tracker.
QtContacts should have been used instead, because that is the
API that is relevant for MeeGo and that corresponds to the one
you used for EDS.
Of course you have a point about the system as a whole, but that still
doesn't make the comparison any better. I could speculate whether this
comparison was skewed intentionally or unintentionally, but let's not go
there, okay?
I've said before and I say it again here, I consider performance
comparisons pointless at this time. Doing them badly just reduces any
good will that might be left from the people one is trying to convince.
--
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.
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
