From kde-devel  Mon Jan 28 22:51:32 2002
From: Thiago Macieira <thiagom () wanadoo ! fr>
Date: Mon, 28 Jan 2002 22:51:32 +0000
To: kde-devel
Subject: Re: QServerSocket: connected, now what?
X-MARC-Message: https://marc.info/?l=kde-devel&m=101225842622560

Erik Sigra wrote
>I derived a type from QServerSocket and created an object of that type. =
It
>seems to work, because I could connect to it with the program stream_sen=
der
>in adasockets-0.1.19/examples. Now what? I can't find any put/get operat=
ions
>in the documentation for QServerSocket.

If you're developing code for KDE, please don't use QSocket or QServerSoc=
ket.=20
Instead, prefer our own alternatives (KSocket, KServerSocket and=20
KExtendedSocket), since they provide more functionality and automatic pro=
xy=20
support.=20

Besides if a user turns global proxy support on, he expects all KDE=20
applications to use it.

Now, as for the API functionality from a server socket, all it does is=20
accept(2) another socket. From there, you get to the normal socket=20
operations. If you're using QServerSocket, you'd get a QSocket. If you're=
=20
using KServerSocket, that's KSocket you get. As for KExtendedSocket, you =
get=20
another KExtendedSocket.

If you have problems using the KDE socket API, let me know. (Constructive=
)=20
Criticism and bug reports are also welcome.

--=20
  Thiago Macieira - UFOT Registry number: 1001
 thiagom@mail.com
   ICQ UIN: 1967141  PGP: 0x8F2978D5 and 0xEA9037A5 (PGP 2.x)
     Registered Linux user #65028

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<