On Tue, Mar 8, 2011 at 1:37 PM, David Woodhouse <[email protected]> wrote: > On Tue, 2011-03-08 at 12:41 +0200, Vitaly Repin wrote: >> Good point. It is closed-sourced. This was a business decision. Has any >> MeeGo guy except the MfE developers ever tried to talk about open-sourcing >> of the MfE solution? >> >> Rhetorical question. > > I've been looking at ActiveSync support recently, so I can answer it > even if it was intended to be rhetorical. > > To be honest, I've found the existing MfE solution on Maemo to be so > horridly broken and unreliable that I didn't even explore the option of > using it. It loses sync for some reason almost every week, and gives me > *no* sensible error messages about what went wrong. > > (I appreciate that coherent error handling is out of fashion in MeeGo, > and baffling the users with silent failure seems to be the norm now, but > I'm old-fashioned and I prefer to buck the trend here.) > > The solution we're looking at for ActiveSync is probably going be a > dæmon which implements the protocol itself, can run in the background > and handle 'push' from the server, etc. The dæmon would be under a BSD > or Apache licence. > > Then we have plugins for SyncEvolution and $MAILER which talk to that > dæmon over DBus. > > This way, the plugins for sync and mail frameworks can be properly > integrated with the code that they plug in to; it's only the ActiveSync > dæmon which has special licensing conditions in some parts of the world.
No idea if its suitable but evolution-mapi at least works with exchange not sure of the difference between mapi and active sync support. Peter _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
