On Mon, 2010-11-22 at 16:17 -0500, Matthew Barnes wrote:
> I'll ponder on this some more. I don't want to get too far off on a
> security tangent right now since this key file proposal is already a
> tangent from migrating to GSettings. But it's good to discuss now so I
> can come back to it later.
Just to follow up, I came up with a simple way to store network security
information in the key file that should work for all backends. Here's a
snippet from my notes:
Schema: org.gnome.Evolution.Source.Security
----------------------------------------------------------------------
[extensions/security]
----------------------------------------------------------------------
method : 's' ('none', 'tunnel', 'starttls', etc.)
So this is illustrating a key file group named [extensions/security]
which uses the GSettings schema "org.gnome.Evolution.Source.Security",
and that schema defines a single string key named "method".
If the user elects not to use a secure connection, it'll look like:
[extensions/security]
method='none'
For backends with a simple "use secure connection" checkbox, they would
just check whether or not the value is 'none' and place some other value
there ('tls' or something, doesn't matter) to indicate yes.
For mail accounts and backends that offer a combo box of security
choices as discussed earlier, the value for 'method' can be more
meaningful such as 'tunnel' or 'starttls'.
I'm not gonna predefine a fixed set of choices for this key. Backends
can write whatever they want there, and that leaves room for additional
security methods in the future.
I'll post the rest of my schema notes and more details about API breaks
in the coming days.
_______________________________________________
evolution-hackers mailing list
evolution-hackers@gnome.org
To change your list options or unsubscribe, visit ...
http://mail.gnome.org/mailman/listinfo/evolution-hackers
