IssueVendorTransfer() handle

[Rob]

We are investigating a handle-resource issue (see my other post).
On of the suspects is an USB driver (written by us).

My question is :
IssueVendorTransfer() returns an USB_TRANSFER handle, should this handle be
closed after this call ? In samples I donot see this....

Kind Regards,
Rob.
www.robtso.nl

[R. de Gravelaine]

Hi,

> IssueVendorTransfer() returns an USB_TRANSFER handle, should this handle be
> closed after this call ? In samples I donot see this....

USBD IssueVendorTransfer returns an USB_TRANSFER handle which is
actually a STransfer * obtained by calling GetTransferObject. This
object is allocated dynamically by USBD and is not a regular system HANDLE.

The IssueVendorTransfer flavor that comes with the samples is the one of
usbclient.c and returns a DWORD. Internally, if no notification routine
is given, the USB_TRANSFER allocated by calling USBD's
IssueVendorTransfer is closed. If a notification routine is provided, it
should close the transfer, eventually after having retrieved the
transfer status.

HTH
Remi