I should mention a couple TODOs: -JavaxUsbPermission is neither finished nor used. Security needs to be clearly defined and implemented in this API, and it isn't yet.
-'Policies' are not present yet. These were initially discussed to solve problems such as in-Java claiming and opening exclusively. For example, a second UsbInterface.claim() method could be added that takes a ClaimPolicy (or something) object. The ClaimPolicy would have methods such as allowRelease(), allowOpen(), etc. that determine if a specific UsbInterface.release(), UsbPipe.open(), etc. is allowed or not. There could be a key associated with the policy that calls to release(), open(), etc. had to use. This solves the problem of non-exclusive access within a JVM. When a Thread (i.e. application) calls UsbInterface.claim(), the interface is claimed and the pipes can be used; but there is no way to limit access to that application or Thread, so any Thread within that JVM can access all parts of the UsbInterface and UsbPipes. -More specific UsbExceptions are required. Especially for submission errors, there need to be specific UsbExceptions like NoBandwithException, TimeoutException, etc. -- Dan Streetman [EMAIL PROTECTED] -------------------------------------------------- 186,282 miles per second: It isn't just a good idea, it's the law! ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ javax-usb-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
