#6 UsbPipe and UsbPipeOsImp List submission too liberal

[Dan Streetman]

The submission methods for Lists allow the OS imp to
decide whether or not to continue processing the List or
abort the remaining UsbIrps, however the UsbPipe API
specifies (as of 0.10.2) that a failure must prevent the
remaining UsbIrps from being submitted (i.e. all remaining
must fail). The APIs must agree on the required behavior.

The required behavior is difficult to mandate, as
sometimes List processing should continue (e.g. a List of
ISO UsbIrps), while in other cases the List should
(probably) not continue (e.g. the device gets into a bad
state). The best policy may be to continue processing
the List...?

[Dan Streetman]

Logged In: YES
user_id=23654

The UsbPipe API submission methods also must be refined.
The current API allows the implementation to decide what
action to take on error in a List, however this should be
refined. There are some cases where continued processing is
required (e.g. isochronous). No cases are known where failing
the remaining UsbIrps should be required, so most likely the
best policy is to continue processing. However a way to allow
the user to specify the policy is probably best. This is either a
API doc change (behavior change) and/or a actual API
interface change, if a user-settable policy is added.

[Dan Streetman]

Logged In: YES
user_id=23654
Originator: YES

Moving to feature request.