Update on KIO & KSSL

[Allen Winter]

On Tuesday 04 September 2007 2:10:43 pm Thiago Macieira wrote:
> Allen Winter wrote:
> >On Tuesday 24 July 2007 9:22:57 am Thiago Macieira wrote:
> >> Will Stephenson wrote:
> >> >On Monday 23 July 2007, Thiago Macieira said:
> >> >> And about KSSL: someone has to work on it. I said I'd do it, but I
> >> >> still have not found the will to start working on it. I do have the
> >> >> will to work on KIO::Job though.
> >> >
> >> >I don't have the skills to do it, but maybe I can help you find the
> >> > will to work on it (where there's a Will, there's a way, boom boom).
> >> >  My porting of everything Groupwise is blocked on KSSL.  You were
> >> > planning (coming out of the QCA/smartcard discussion) to port to
> >> > QSSLSocket. What else did you have in mind for KSSL besides
> >> > cleanups?
> >>
> >> Complete overhaul.
> >>
> >> That is, the new API has to be written. Currently there is no SSL
> >> support at all outside libkio. The support inside is there only
> >> because we can't disable https.
> >
> >This is becoming a major impediment to further progress on KMail.
> >What can we do to get KSSL development up and running?
> 
> Unfortunately, the answer is "find someone to do it". I don't have time 
> right now to write a complete API.
> 
That's what I'm trying to do :)

> The best I can do is QSslSocket. So, if someone thinks QSslSocket is 
> inadequate, do something better, now.
> 

I don't know anything about this topic.
What would a new KSSL class provide that the QSslFoo classes don't?
Would be be better off simply porting our apps to use QSslFoo instead of KSSL?

Thiago, I guess I'm looking for a mini-design description of a new KSSL.

-Allen