While I suppose this one is rather hard to fix, too, kindly check whether the following proposal is good enough to be implemented to finally get rid of this issue. If I am not mistaken, when the client is truly connected, then there must be users available on the hub, at least one, which is the client itself. Based on this I was thinking of whether it would be possible to do a user count several seconds after the client receives the connected state, and if the amount of the users cannot be determined (or equals zero), then an automated reconnect should be issued by the client itself.
-- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to DC++. https://bugs.launchpad.net/bugs/190964 Title: Rare connection hang, on joining a hub Status in DC++: New Bug description: This happened in 0.699 a lot more than now, but it still happening in svn 1000. Sometimes (not very often) on connecting to a hub it sticks. (i did report this on bugzilla just before it disappeared). From hubframe [14:34:17] *** An existing connection was forcibly closed by the remote host. [14:34:21] *** Connecting to blah... [14:34:22] *** Connected [15:33:50] *** Disconnected <---- manual reconnect done here [15:33:50] *** Connecting to blah... [15:33:51] *** Connected [15:33:54] *** Stored password sent... To manage notifications about this bug go to: https://bugs.launchpad.net/dcplusplus/+bug/190964/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
