mail_session_add_service(): Make display-name binding one-way.

We're leaking CamelService references when we remove a CamelService
from a CamelSession.  I don't yet know where or how.

If we remove a CamelService without finalizing the corresponding ESource,
and then add a new CamelService with the same UID, the ESource will have
a bidirectional "display-name" binding to multiple CamelService instances.
This creates an endless cascade of "notify" signals as soon as any of the
bound "display-name" properties change.

Until I can fix the leaking CamelService references, make the binding
one-way: ESource -> CamelService.  This means the ESource's display name
is authoritative, and camel_service_set_display_name() MUST NOT be called
explicitly or else it will become out-of-sync with the ESource.

0 files changed, 0 insertions, 0 deletions