Very good ! ☺ Envoyé depuis mon smartphone Samsung Galaxy. -------- Message d'origine --------De : "Enrico Weigelt, metux IT consult via Maildev" <maildev@lists.thunderbird.net> Date : 12/08/2017 05:14 (GMT+02:00) À : maildev@lists.thunderbird.net Cc : "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net> Objet : [Maildev] hard dependencies on addrbook component Hi folks, I've just seen that many places (eg. composer) depend directly on the addrbook component, while they'd just need the addrbook service interfaces. That somewhat contradicts the whole idea of components / services and as consequence we can't easily replace different parts (frontend vs. database backends, etc). Therefore, I propose splitting it up into several pieces: move out the service interfaces (eg. nsIAB*) to an own component, as well as the actual service. Later on, we could even think about an splitting further into several storage services (local db's, ldap, carddav, ...) vs. some aggregating/meta service from mapping them together (which will be called by clients like composer, gui, etc) What do you think about that ? --mtx _______________________________________________ Maildev mailing list Maildev@lists.thunderbird.net http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net