# [Meego-architecture] [MeeGo-dev] Some architecture changes (MSSF / Buteo / PIM storage)

Vitaly Repin vitaly.repin at nokia.com
Tue Mar 8 02:31:56 PST 2011

Hello,

On Tue, 08 Mar 2011, ext Adrien Bustany wrote:

> Synchronization is a solved problem, mind you, our mail for exchange
> plugin does a pretty good job at saving contacts in a slow way. Using
> APIs the right way, it could sync 500 contacts in 80 seconds, as
> mentioned above.

I am very sorry but I have to state the following items here:

1) Exchange implementation has taken into use ALL your and Contacts team
guidelines/directions to improve the contacts synchronization speed.
2) We are not aware of any "improper" API usage at this point of time.
3) I would be really happy to hear the new suggestions from you or
Contacts team to improve the situation. In form of bug reports, coming
to my desk in Ruoholahti, emails, phone calls. Anything!

\begin{"take it personally" mode}
- Exchange team was the first team which has shown the problem with
Contacts sync speed. Yes, our guy, not somebody else, have filed
that famous bug about the contacts speed.
- The first response was - don't even expect the contacts speed to be better
than we have now (and it was really slow that days. REALLY.)
- We have spent a lot of energy / time to convince the teams in Nokia MeeGo to fix
their stuff, changed the way we used their APIs etc. The end result -
the contacts sync. speed has improved a lot. Not only for us but for
everybody.
- And now we are getting the very "positive" feedback in public mailing list from
our colleagues just because we are closed-sourced (thanks to the managers!) and