LibusbJava

libusb for Java

User Tools

Site Tools


implementation:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
implementation:start [2015/07/01 14:45] – created ursgrafimplementation:start [2016/02/25 13:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Implementation ====== ====== Implementation ======
-In libusb, the bus structure (with devices, configurations, interfaces and endpoints) is represented in C structs. These structures are kept there, no Java object are created (named Usb_xxxand the information is copied to this objectThis is done when calling LibusbJava.usb_get_busses(). The information about busses and attached devices can now be obtained from a tree like Java Object structure. +In libusb, the bus structure (with devices, configurations, interfaces and endpoints) is represented in C struct's. These structures are kept there, no Java object are created out of them. In the C/C++ wrapper we keep the native (libusbdevice pointers. Every call from Java is initiated over this device pointerSo we can be sure to access at any time most actual USB information the libusb has. \\ 
- +In Java you can access the descriptors with a tree-like object structure and you don't have to worry about the internal pointers and struct's
-It provides a simple Device class which represents USB device and makes it easy to write to and read from it. Errors and Timeouts will result in Exceptions.+This tree-like object structure provides a simple device class which represents an USB device and makes it easy to write to and read from it. Errors and timeouts will result in exceptions.
  
  
 ====== Versioning ====== ====== Versioning ======
 +The version numbers of the libusb and our LibusbJava are intertwined. The following figures shows all necessary details. 
 +[{{:implementation:versioning.png?600|}}] 
implementation/start.1435754717.txt.gz · Last modified: 2016/02/25 13:33 (external edit)