From kde-core-devel  Thu Jun 20 15:04:57 2002
From: Thiago Macieira <thiagom () wanadoo ! fr>
Date: Thu, 20 Jun 2002 15:04:57 +0000
To: kde-core-devel
Subject: Re: QSocket problem with transconnect (proxy)?
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=102458809204869

Michael Goffioul wrote
>I modified the patch a little bit to emit the connected signal after the
>read notifier has been enabled, as in tryConnection(). However I still
>don't know how d->addr can be different from 0.0.0.0.

My thoughts exactly. d->addr is referenced only once in the code, and it's=
=20
read. My guess is it DOESN'T work at all.

The thing is, this problem had never shown up because all the connections=20
returned EINPROGRESS, which meant that the code in QSocket::tryConnection()=
=20
always got called. However, since there was a connection in progress,=20
QSocketDevice::connect() didn't try again to connect.

QSocketDevice::connect() doesn't seem to behave the same way when the socke=
t=20
is already connected.

Care to do the honours and send the patch and the bug case to the trolls?

=2D-=20
  Thiago Macieira - UFOT Registry number: 1001
 thiagom@mail.com
   ICQ UIN: 1967141  PGP: will create new keys. Erase the old ones!
     Registered Linux user #65028