Differences

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

--- implementation:start [2015/07/04 15:11] – [Versioning] ursgraf
+++ implementation:start [2016/02/25 13:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== 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 out of them. In C/C++ we keep the native (libusb) device pointer and from there, every call from Java is initiated over this device pointer. So we are sure we have everytime the most actual USB information libusb has. \\
+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 (libusb) device pointers. Every call from Java is initiated over this device pointer. So 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 structs.
+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.
+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.
-It provides a simple Device class which represents a USB device and makes it easy to write to and read from it. Errors and Timeouts will result in Exceptions.
 ====== Versioning ======
 The version numbers of the libusb and our LibusbJava are intertwined. The following figures shows all necessary details.
-{{:implementation:versioning.png?600|}}
+[{{:implementation:versioning.png?600|}}]

LibusbJava

User Tools

Site Tools

Differences

Page Tools