Skip to content

It's so weird...

Friday, 9 March 2007  |  thiago

It's so weird to start writing Yet Another Networking Framework (YANF) for KDE...

It's weird not because it's simply YANF. It's weird because this is the fourth networking framework that I will have written for KDE. So, a little history:

  1. KDE 1.0 came out with a KSocket and a KServerSocket class, by Torben Weis
  2. During the KDE 2.0 development phase, I started to write something different, to support IPv6. This never made it to mainline KDE because I did not submit it. But here's the proof that I did: my blog from Aug 17th, 2000
  3. Later, when KDE 2.2 was in development, I started to write the KExtendedSocket class, that actually made it to the release. Here's the blog from Dec 2nd, 2000 to prove
  4. As a general consensus, KExtendedSocket was found to be bloated and difficult to understand. So I proposed a new framework, simpler and more robust. In fact, I proposed that it become part of Qt, but that didn't happen. Nonetheless, it did influence Qt 4's QtNetwork library. But it turned out to be the current KNetwork framework in kdecore. Here's the blog showing me starting to work and the initial proposal email from Jan 14th, 2003
  5. After Trolltech announced support for proxies and SSL in QtNetwork last week, I decided it was time to merge KNetwork and QtNetwork (one could say they are two children of the same idea, above). So, I sent this email entitled "RFC: Drop notice: KNetwork" to kde-core-devel

The new framework will be basically a wrapper around QtNetwork to provide the two missing features: Unix sockets and SVR-based lookups. The rest we can do without. And even then, Trolltech seems to be interested in providing Unix sockets in QtNetwork itself.