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

List:       kde-games-devel
Subject:    Re: [Kde-games-devel] Client-Master
From:       Burkhard Lehner <Burkhard.Lehner () gmx ! de>
Date:       2001-04-12 14:02:41
[Download RAW message or body]

Hi, Developers!

Am Thursday 12 April 2001 01:47 schrieb George Staikos:
> On Wednesday 11 April 2001 17:59, Andreas Beckermann wrote:
> > Burkhard: Do you still want to port libkdegames to QSocket instead of
> > KSocket? If so then KGameClientSocket is the place for you :-)
> > You won't break anything except network games now - ie you don't have to
> > care about the process player anymore. The port should be a lot easier
> > now
> >
> > :-)
>
>   If you use QSocket instad of KSocket then you will lose support for ipv6
> and SOCKS.

Who can help me??? I'm very confused!!!

Looking in the KDE 2.1 API reference
(http://developer.kde.org/documentation/library/2.1-api/classref/kdecore/)
says that there is a new class KExtendedSocket, with a lot of nice features. 
But downloading the KDE 2.1 kdelibs package
(ftp://ftp.fu-berlin.de/pub/unix/X11/gui/kde/stable/2.1/distribution/tar/generic/src/kdelibs-2.1.tar.bz2)
doesn't contain any such files or classes!

Now, what's wrong here? I suppose it is just as it is always in KDE: The 
developers API documentation is always horrible and is never up to date with 
the real packages! Or is the kdelibs package I downloaded somewhat old or 
wrong?

So, can anyone tell me where to find the REAL KExtendedSocket class?

I wanted to look into the class sources, because the API documentation 
doesn't mention such important features as "non blocking host lookup". Does 
KExtendedSocket have something like this? QSocket has, I know for sure! And I 
think one shouldn't write a program that hangs on queries to DNS services.

So, we again have a discussion about which socket classes to use. Here the 
pro's and con's:

KSocket:
  - no non-blocking DNS lookup
  - very difficult to handle incoming and outgoing data
  + supports SOCKS (not build in, but as another class using KSocket)
  + supports IPv6 (does it really? I'm not sure!)
  - using it will mean you have to link in libkdecore

KExtendedSocket:
  - so many low level functionality one never needs
  -/+ does it non-blocking DNS lookup? Who can tell me?
  -/+ does it buffered input and output?
  + subclass of QIODevice, so QDataStream can work on it directly
  + supports IPv6
  - using it will mean you have to link in libkdecore
  - is there already a SOCKS class for KExtendedSocket? I don't think so

QSocket:
  + well documented, very stable
  + is does non-blocking DNS lookup
  + subclass of QIODevice, so QDataStream can work in it directly
  - doesn't support IPv6 yet (AFAIK), but will soon, binary compatible
  - doesn't support SOCKS, but a class could easily be created
  + no need to link in libkdecore
  
So, in my opinion, KExtendedSocket or QSocket should be the way, but since I 
don't know KExtendedSocket yet, I would prefer QSocket.

Please help me! Where do I find KExtendedSocket?

Bye,
	Burkhard

----------------------------------------------------------------
Burkhard Lehner                         Burkhard.Lehner@gmx.de
Pfaffenbergstraße 101                      Tel: (0631) 1 03 63
67663 Kaiserslautern                    Fax: (0631) 3 10 52 15
               http://www.burkhardlehner.de/
_______________________________________________
Kde-games-devel mailing list
Kde-games-devel@master.kde.org
http://master.kde.org/mailman/listinfo/kde-games-devel

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