When creating fully asynchronous application, the guarantee that all callbacks
happen in libusb_handle_events_*() is good. However, the hotplug implementation
breaks this guarantee - new thread is forked and the hotplug callback is called
from alternate thread. This means application needs to do locking and
inter-thread message passing.
It would be better for the hotplug implementation to use internally the same
asynchronous mechanisms, and do it's processing libusb_handle_events_*() to
allow proper single-threaded application implementation.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/158
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
