From kde-core-devel  Mon May 21 00:03:43 2001
From: Waldo Bastian <bastian () kde ! org>
Date: Mon, 21 May 2001 00:03:43 +0000
To: kde-core-devel
Subject: Re: RFC: TLS default enabled/disabled?
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=99040355925048

On Sunday 20 May 2001 14:29, Michael Häckel wrote:
> On Friday, 18. May 2001 20:29, Waldo Bastian wrote:
> > Again, this is an ugly hack which isn't necassery any longer. The URL
> > should indicate _what_ you want to fetch, not _how_ you want to do that.
> > Use slaveConfig() to specify how. You can then put default values in
> > kio_smptrc which will be used unless the application overrides them.
>
> Back on my main computer I had a look at SlaveConfig, however somehow it
> doesn't really fit the needs required for storing information about using
> TLS or not.
>
> At least from the point of view of the user, I would like to add a checkbox
> to for example the IMAP account config dialog which allows to set this
> option for every account as it is possible to check the option for SSL
> already. This appears to me to be the natural way of doing this.
>
> Using SlaveConfig, this fails at least, if the user has two accounts on the
> same server. Ok, usually then TLS is also supported on both accounts, but
> the user might wonder, why the other checkbox also changes, when he
> actually changed only one of them.

Yes, no I wouldn't use it like that. In KMail you run your slave in 
connection orriented mode, so I would just pass all the info for a certain 
account as "Config". E.g. with a call to "slave->setConfig()"

The host-based configuration that the SlaveConfig class provides isn't very 
usefull for KMail and is more intended for protocols like http or ftp.

Cheers,
Waldo
-- 
bastian@kde.org | SuSE Labs KDE Developer | bastian@suse.com