KSSL session reuse bugs

[Stefan Rompf]

Hi,

> [ process local cache for private certs ]
>
>   We used to have this but we had to get rid of it due to synchronization
> issues (ca. KDE 2.2).  Too many slaves and apps concurrently accessing and
> modifying the database was a problem.

this may be a problem. However, I don't expect the information which 
certificate should be send to which host to change that much. Checking 
certificate validity after the connection has been made is something 
different.

>    This is a more generic problem.  I think it goes to show that we need a
> slightly different approach for sessions.  Nevertheless, the current
> implementation certainly shows big performance improvements over KDE 3.1. 
> I think it's quite worthy in that respect. :)

Of course, no doubt about that ;-) I just want to take my chance to make it 
better.

Right now I'm testing a change that moves session handling into KIO::
TransferJob. I hope that this solves all my problems beside following 
redirections. For security reasons, I don't use kssld, see my answer to 
Waldo.

Patch is attached, also for review by David.

Stefan
-- 
"doesn't work" is not a magic word to explain everything.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kio.diff
Type: text/x-diff
Size: 3000 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20031023/f2339786/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1691 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20031023/f2339786/attachment.bin>