From kde-core-devel Thu Sep 30 15:25:48 2004 From: Thiago Macieira Date: Thu, 30 Sep 2004 15:25:48 +0000 To: kde-core-devel Subject: Re: Migrating Qt Cryptographic Architecture to KDE CVS Message-Id: <200409301225.49481.thiago.macieira () kdemail ! net> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=109655804321405 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart2115633.Dht9XQ6YN2" --nextPart2115633.Dht9XQ6YN2 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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.= =20 Think of DCOP, for instance. I agree with you that the classes are in the=20 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. =2D-=20 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 --nextPart2115633.Dht9XQ6YN2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQBBXCV9M/XwBW70U1gRAtF7AJ0YG1NLZi5bXs7/skrMu1/7xiipLwCghs2r IGWg5jI7MtwNtTrUAnf6W00= =ycqG -----END PGP SIGNATURE----- --nextPart2115633.Dht9XQ6YN2--