Bug 1819 - SqueezeNetwork connection timeout is too short
: SqueezeNetwork connection timeout is too short
Status: RESOLVED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Misc
: 13
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-14 05:05 UTC by Max Spicer
Modified: 2009-09-08 09:12 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Max Spicer 2005-07-14 05:05:02 UTC
My ADSL router is set to disconnect from the internet when it's not in use.
Therefore, when I connect to SqueezeNetwork, my connection is often not up. When
I attempt the connection, this causes my router to connect to the internet, but
this takes around 5-10 seconds. During this time, the SB2 reports that it can't
connect and I have to tell it to try again, at which point it succeeds. I think
the timeout should be increased to avoid this - it can't be that unusual a
situation, and it's clumsy when it occurs.

(see http://forums.slimdevices.com/showthread.php?p=44364 for a possible discussion)
Comment 1 Vidur Apparao 2005-07-14 08:41:57 UTC
Reassigning to Dean - he recently changed the DNS timeout.
Comment 2 Blackketter Dean 2005-07-14 08:51:27 UTC
I'm tempted to leave the behavior as-is.  You shouldn't have to do anything for it to eventually connect, 
but the warning will remain. (Eventually the screen should blank-out if it really can't connect.)

Please confirm that it does eventually connect (though display the warning).
Comment 3 Max Spicer 2005-07-15 01:19:25 UTC
It does eventually connect.  I think the error message is ugly though, and
probably scary for the non-technical Squeezebox owner.  Many devices/programs
have to put up with waiting for a connection to come up and yet you never see
connection failed errors from them.  Maybe the error message could be made to be
more an informational message, something like "connection could not yet be made,
retrying...".
Comment 4 Blackketter Dean 2005-07-15 07:33:15 UTC
agreed, the error shouldn't be displayed in so short a time.
Comment 5 Blackketter Dean 2005-09-07 15:00:04 UTC
10 seconds in the latest nightly