Waldo Bastian wrote:
> > KSocket has so few consumers IMO, there should be no KExtendedSocket.
> > Just replace or extend KSocket.
>
> It's virtually unused in KDE itself but it is being used by third parties
so
> we need to maintain backwards compatibility.

Not only that, the way I designed KExtendedSocket, it has become quite
large. Just take a look at the number of protected member variables.
Also note KExtendedSocket is a descendant of QIODevice. For one
socket, it's ok to use it. But if the program will keep several
connections open... I don't want to increase unnecessarily the memory
footprint of KDE programs. The idea is to have KSocket's constructor
or underlying function create a KExtendedSocket object, have it
connect, then delete the object, keeping the connection/socket open.
That way, I believe, KSocket will be kept small.

Anyways, I did not go through all the code to look for uses of
KSocket. But I did look for uses of ::socket() et alii, because they
should not be there. TCPSlaveBase had one such at the time of KDE
1.92.

--
  Thiago Macieira - UFOT Registry number: 1001
 thiagom@mail.com talha@geocities.com
   ICQ UIN: 1967141  PGP: 0x8F2978D5 and 0xEA9037A5
     Registered Linux user #65028

171/378. Yes, ma'am. Its ion signature leads directly to
that...whatever it is. -- Ens. Tom Paris, "Dark Frontier, Part II"