[Evolution-hackers] Might be a generic ESourceExtension useful?

[Milan Crha <mcrha redhat com>]

	Hi,
I was wondering, after the all stuff around ESourceExtensions landed in
3.5.x, the main disadvantage of it is code duplication, or passing
unrelated stuff into one public folder just to have them available. It
is, for example, when a backend defines its own extension, because it
has some configuration, but the configuration part, which lands in
evolution, also requires this extension, hence the code duplication.

What about solving such issue with a generic ESourceExtension, which
will provide similar interface like the GKeyFile (it is GKeyFile, after
all), and the "clients" will be able to check for availability, read
from or write to any section and key, thus instead of code duplication
there will be set of "well-known" sections and keys?

I thought there will be such a thing from the beginning, but Matthew
chose a different approach. I think the generic extension would be
useful. What do others think?
	Bye,
	Milan