[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: Migrating Qt Cryptographic Architecture to KDE CVS
From: Thiago Macieira <thiago.macieira () kdemail ! net>
Date: 2004-09-30 15:25:48
Message-ID: 200409301225.49481.thiago.macieira () kdemail ! net
[Download RAW message or body]
Jason Keirstead wrote:
>Personally, I think there is something wrong with the way kdelibs is
>tructured. The KDE network classes (and there a lot of them now) shouldn't
> be in kdecore at all. Many KDE apps have no need network connectivity at
> all and this is just extra baggage. There should be a seperate kdenetwork
> library that depends on kdecore, and kio can depend on kdenetwork. The
> SSL stuff can go in here.
All KDE applications require network connectivity of one level or another.
Think of DCOP, for instance. I agree with you that the classes are in the
wrong place: they should be in Qt or even lower.
The result of that is that neither libDCOP nor aRts can use those classes.
>Even if you did this though. that would still mean that kdenetwork would
> need kdeui for the certificate dialogs. No idea how to resolve this
> dependancy.
SSL classes: libqca
network classes: libkdecore
certificate management and UI: libkio
KSecureSocket could go in either of the latter two.
--
Thiago Macieira - Registered Linux user #65028
thiago (AT) macieira (DOT) info
ICQ UIN: 1967141 PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
[Attachment #3 (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic