[Libusb-win32-devel] usb_interrupt_read timeouts

[Dave H. <DAV...@ni...>]

In the Linux version of libusb, the usb_interrupt_read () function can
accept a value of 0 for the timeout, which is interpreted as "infinite".
In the win32 version, this is not accepted.  OK, I can put any finite
timeout that I choose, and loop round infinitely on a separate thread,
putting any resulting input into a FIFO.

But what happens if a USB message comes in immediately after the
timeout, but before the new call?  Is any such message lost?

Dave


***************************************************************************=
***************************************************************************=
***************************************************************************=
****************

NICE CTI Systems UK Limited ("NICE") is registered in England under company=
 number, 3403044.  The registered office of NICE is at Tollbar Way, Hedge E=
nd, Southampton, Hampshire SO30 2ZP.

Confidentiality: This communication and any attachments are intended for th=
e above-named persons only and may be confidential and/or legally privilege=
d. Any opinions expressed in this communication are not necessarily those o=
f NICE. If this communication has come to you in error you must take no act=
ion based on it, nor must you copy or show it to anyone; please delete/dest=
roy and inform the sender by e-mail immediately.

Monitoring: NICE may monitor incoming and outgoing e-mails.

Viruses:  Although we have taken steps toward ensuring that this e-mail and=
 attachments are free from any virus, we advise that in keeping with good c=
omputing practice the recipient should ensure they are actually virus free.

***************************************************************************=
***************************************************************************=
***************************************************************************=
*******************

=20