On 03/19/2012 07:38 PM, Scott Talbert wrote: > On Sun, 18 Mar 2012, Phil Dibowitz wrote: > >> +const int connect_timeout = 2; // try to connect for 2 seconds >> >> Does 1 work well for the usbnets? Its not a big deal, but I think it'd be a >> better user experience for everyone else. > > Okay, so for the most part, 1 second timeout is fine for usbnet. The only > possible issue is upon initial plug-in of the remote. On average, it > takes about 5 seconds for the remote's IP interface to become operational > (I think most of this is just waiting for the remote to issue its DHCP > request.) So, if someone plugs in their remote and then tries to do > something with it in the first 5 seconds, it is going to fail. Do you > think this is acceptable?
I don't think we have a choice. :) In any case, the shorter the timeout here, the faster we retry the quicker we'll notice the interface come up and the faster they can do something, right? -- Phil Dibowitz p...@ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
