On Tue, 20 Mar 2012, Phil Dibowitz wrote: >>> I'm wondering if we want to figure out that it's a usbnet remote by USB >>> vid/pid and behave differently. We can short-circuit FindRemote, if we don't >>> find a remote, we can print a message saying that we're waiting for 5 >>> seconds >>> for the remote to be configured on the network, etc... >> >> How about this (slight variation): if FindRemote discovers a known usbnet >> pid, we pass that information along to FindUsbLanRemote and in that case, >> we extend the timeout. > > I'm fine with that. We can return early from FindRemote with a code that says > this is usbnet, and then pass that to usbnet. If we're going to do that, we > should probably be smart and once we know what kind of remote it is not call > the other one, ever again... > > I'm fine if you want to do that work now, or if you prefer to just print a > message when we don't find a remote that >900 models may take several seconds, > and we can come back to this later, that's fine too.
Eh, let's just go with the latter option for now. I've added something in v8. ------------------------------------------------------------------------------ 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
