On Jul 4, 2006, at 10:51 AM, Andy Grundman wrote:
On Jul 4, 2006, at 10:44 AM, atlslim wrote:
I have a device on a strange subnet that I am not able to identify or
disable. SlimServer (latest trunk) has the same problem:
2006-07-04 10:28:09.7697 SimpleAsyncHTTP: GETing
http://192.168.2.1:5678/igd.xml
2006-07-04 10:28:09.7857 AsyncHTTP: Connecting to 192.168.2.1:5678
2006-07-04 10:28:30.8273 Select Task > 0.5 : 21.0623281002045
2006-07-04 10:28:30.8376
Slim::Networking::UPnP::ControlPoint::_readResult
2006-07-04 10:28:30.9064 Response Time > 0.5 : 21.1550059318542
2006-07-04 10:28:30.9304 AsyncHTTP: timed out, failed to connect
The problem is that the attempt to connect repeats (X4) and
significantly delays server startup.
Any way to adjust this??
The connection attempt is made asynchronously and should not delay
server startup at all. If it is, it's a bug. I will test again
with an unreachable device and see if it works for me.
After any UPnP request fails, it won't attempt to connect to that
device again for 30 minutes. The reason the connection attempt
repeats is probably because the device sends out many notify
packets at once. My wireless router sends out like 10 notify
packets because of all the different services it offers. I'm
guessing your mystery device is a router (because of the "igd.xml"
which probably stands for internet gateway device).
I checked in a change that should take care of the multiple requests,
it should now only make one request. I tested with an unreachable
device and it didn't cause any problems with the responsiveness of
SlimServer.
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/beta
