On Thu, May 14, 2015 at 12:22 AM, Olaf Meeuwissen <[email protected]> wrote: > m. allan noah writes: > >> Stef did some work a few years ago on sanei_configure_attach, which >> might fill the need. > > I may take a look. The thing is that backend configuration and device > detection are two separate things. The epson2 backend doesn't read its > configuration file unless you do device detection. That smells. > >> In the short term, I will say that my backends all call >> sane_get_devices inside sane_open if there is no cached list of >> devices. > > There should be no need to do that. You either open the device that was > passed or the first supported device you find if the default was > requested. There is no point in trying to find all the the available, > supported devices in sane_open(). It would seriously suck if a call to > sane_open() for a *specific* device would end up doing, for example, a > broadcast for networked devices on a reasonably sized subnet with a ten > seconds timeout.
Agreed, but there is configuration for the requested device in the config file, and finding it can be a pain. If I ever work on a backend with network support, I would have to change that. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" -- sane-devel mailing list: [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to [email protected]
