[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: RFC: TLS default enabled/disabled?
From:       Waldo Bastian <bastian () kde ! org>
Date:       2001-05-21 16:53:57
[Download RAW message or body]

On Monday 21 May 2001 00:19, Michael Häckel wrote:
> On Monday, 21. May 2001 07:21, Michael Häckel wrote:
> > On Monday, 21. May 2001 02:03, Waldo Bastian wrote:
> > > 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.
> >
> > Thanks for the hint.
>
> Sorry, but there is a problem with that. While passing configuration to
> operations like KIO::get, this does not seem to be possible for opening the
> connection.
>
> If I execute
>
> mSlave = KIO::Scheduler::getConnectedSlave(getUrl());
> if (!mSlave) return FALSE;
> mSlave->setConfig(mSlaveConfig);
>
> in openConnection() the values are not yet there.
>
> Do I have to create the slave myself, or is there a way around this?

Ok. Update kdelibs/kio and then you can use:
mSlave = KIO::Scheduler::getConnectedSlave(getUrl(), mSlaveConfig);

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

[prev in list] [next in list] [prev in thread] [next in thread]