Re: libusb future

by Xiaofan Chen :: Rate this Message:

On Jan 3, 2008 7:16 AM, Tim Roberts <timr@...> wrote:

> I'm torn about how to handle the naming of sync vs async routines, even
> in my own code. Although "libusb_submit_bulk_urb" accurately reflects
> what the routine does, in fact the libusb user doesn't know about or
> think in terms of URBs. That is an implementation detail.
>
> I could be talked into this:
> libusb_submit_bulk_transfer
> libusb_submit_bulk_transfer_async
> or this:
> libusb_submit_bulk_transfer_and_wait
> libusb_submit_bulk_transfer
>

libusb-win32 0.1 has already implemented isochronous transfer and asynchronous
I/O support.

http://libusb-win32.svn.sourceforge.net/viewvc/libusb-win32/trunk/libusb1/src/dll/usb.h?view=markup

int usb_isochronous_setup_async(usb_dev_handle *dev, void **context,
unsigned char ep, int pktsize);
int usb_bulk_setup_async(usb_dev_handle *dev, void **context,
unsigned char ep);
int usb_interrupt_setup_async(usb_dev_handle *dev, void **context,
unsigned char ep);

int usb_submit_async(void *context, char *bytes, int size);
int usb_reap_async(void *context, int timeout);
int usb_reap_async_nocancel(void *context, int timeout);
int usb_cancel_async(void *context);
int usb_free_async(void **context);

How do you like the above names?

Xiaofan

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Libusb-devel mailing list
Libusb-devel@...
https://lists.sourceforge.net/lists/listinfo/libusb-devel

« Return to Thread: libusb future