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

List:       kde-bugs-dist
Subject:    [Bug 20286] multiple IPs, first one fails
From:       Waldo Bastian <bastian () svn ! net>
Date:       2002-10-31 13:03:43
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=20286     




------- Additional Comments From bastian@svn.net  2002-10-31 14:03 -------
Subject: Re:  multiple IPs, first one fails         

I think that we correctly look up all IPs. Handling of multiple IPs 
while connecting should probably happen in KExtendedSocket::connect() It 
actually does have a loop that seems to iterate over all IPs but I think 
it only tries to use a different IP when no timeout has been specified. 
Another problem is that it will not remember the results of previous 
connect attempts, so if there are two IPs and only the second one works, 
it will keep trying to use the first (failing) IP number first on 
following calls to connect()

This is hard to correct because even if we fix it within a single 
process, io-slaves are all within separate processes so each new 
io-slave will at least have to try the first IP once.
[prev in list] [next in list] [prev in thread] [next in thread]