[Evolution-hackers] ESource, backends

Ettore, Toshok and I just had a discussion on IRC re. what to do with
ESource and how to get parameters across to backends.

What we more-or-less agreed on is that we can pass the ESource to the
backend, encoded as XML. This lets callers use ESources that are not in
gconf, but also allows getting updates from gconf if the ESource has a
UID/path in it (also encoded in the XML).

Thus we avoid the gconf requirement, and the changes to the IDL and
ESource are miniscule (XML serialization code is already there).

JP, thoughts?

Hans Petter

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]