On Tuesday 21 Jun 2011 12:40:04 Sven Burmeister wrote:
Am Montag, 20. Juni 2011, 07:00:32 schrieb Anton Aylward:
- You're hard coding it in rather than making it a plugin option
The plug-in option does not make sense. It would be a duplication of code if e.g. the kdepim address book would have its own methods to talk to ldap and additionally to that the methods to talk to akonadi which then talks to ldap.
FWIW, the plug-in option was tried early in the KDE 4 cycle, by writing KResources (legacy addressbook and calendar API for those who haven't been paying attention) plugins that access Akonadi. This exposed serious flaws in the KResources interfaces for anything other than local, synchronously-available data, which those of us responsible for talking to remote, asynchronously-accessed data (eg the Novell Groupwise KResources, which paid for a lot of openSUSE KDE time :)) had been sort-of- working around for years. (On a side note, the LDAP functions in pre-Akonadi KAddressbook work so well because they are hardcoded into KAddressbook, bypassing KResources) This confirmed that we had a choice between rewriting all the apps around Akonadi, or giving up on progress beyond locally stored single-access data. Your friendly local PIM historian, Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org