Hotplug isn't there yet, and Liam's problem is because the Windows
backend doesn't currently implement what the libusb-1.0 API currently
offers. Without hotplug. This is a bug in the Windows backend.


> >> - is this an appropriate way to manage the process of closing my device?
> >
> > Yes, it is.
> 
> Or rather, it would be, if we had implemented global hotplug support, 

It's the appropriate way to use the libusb-1.0 API both right now and
once a hotplug feature is available.


> > You are the first one to report it, but there have not been very many
> > reports of libusb use on Windows at all, so that doesn't mean much.
> 
> Liam, I'm afraid you'll find that many people on these lists don't
> agree with these kind of subjective statements from Peter.

I guess that Liam gets the point; we don't have much data, so we
can't say that this is a known problem.


> avoid relying on libusb(x) for any scenario that involves hot
> plugging of a device.

libusb-1.0 supports hot-unplug since 2008, but the Windows backend
has a bug in implementing that.


Since Pete doesn't seem interested to fix this I'll repeat the
suggestion for Liam to have a look into the code. Or at the very
least please create a ticket against the Windows backend. Patches
for libusb to fix this right now are certainly welcome!


//Peter

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel

Reply via email to