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

List:       kde-core-devel
Subject:    Re: Migrating Qt Crytpographic Architecture to KDE CVS
From:       George Staikos <staikos () kde ! org>
Date:       2004-09-30 15:56:46
Message-ID: 200409301156.46714.staikos () kde ! org
[Download RAW message or body]

On Thursday 30 September 2004 11:49, Jason Keirstead wrote:
> On September 30, 2004 12:22 pm, Waldo Bastian wrote:
> > KSSL is in KIO. However, KSSL is mostly used by the io-slaves and it's
> > not such a good idea to do dialogs in the io-slaves themselves.
>
> That is the whole point of the conversation. There are other places in KDE
> that use SSL outside of IO slaves, and right now they need to do their own
> certificate handling. So you have either duplicate code everywhere, or you
> have different libraries in use doing the same thing.
>
>  - Kopete
>  - Konversation
>  - *Foo* networking app that wants to use SSL
>
> So that code shouldn't be in TCPSlaveBase, but like you said, it needs ui
> so it shouldnt go into kdecore either. So no one knows where it goes.

  The point is that the code in TCPSlaveBase is specific to TCPSlaveBase.  If 
you want it in Kopete or Konversation, you should adapt that code as 
required.  It could then be packaged into a class or function or whatever is 
most suitable and placed into libkssl for general use.  This is the typical 
way all such code finds its way into kdelibs.

-- 
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/
[prev in list] [next in list] [prev in thread] [next in thread]