device filtering support

[Pete Batard]

On 2012.02.05 00:34, Michael Plante wrote:
> There's one other issue:  versioning.

Yeah, and I thought about that too.

App sends a message indicating whether it can provide a newer version of 
the process (i.e. a version where code has changed. If different 
versions use the same code, no need for action, even if app is newer 
version than the app that launched the enum process) during libusbx_init 
and if newer, the process kills itself and lets the app spawn one.

Oh, and APIs. You set an API for interprocess communication that's as 
static as the libusbx API, so you can update code and still expect old 
apps to work => your concern about protocol breakage is as irrelevant as 
concern about libusb 1.0.10 breaking 1.0.9 apps: we're of course not 
going to break protocols behind the scenes. Whether they belong to the 
user visible part or not, they would very much belong to the libusbx 
API. And if there's 1.0 and 2.0 libusbx apps, there might be 2 processes 
(but probably not if we do things well and don't need to update enum).

I did think about it and didn't identify it as a showstopper.

Regards,

/Pete