Development/ReWrite2010
From Rxtx
(Difference between revisions)
(initial) |
|||
Line 17: | Line 17: | ||
== Milestones == | == Milestones == | ||
+ | To do... | ||
== What is left to be done and known issues == | == What is left to be done and known issues == | ||
Line 24: | Line 25: | ||
== Building the code == | == Building the code == | ||
+ | |||
+ | To do... | ||
[[category:development]] | [[category:development]] |
Revision as of 16:16, 25 February 2011
Contents |
Introduction
The intended objectives and architecture are documented in the RxTX_Rewrite.pdf document in the ReWrite2010 of the in the source repository. To summarise:
Provide a reference implementation of the javax.comm package using open source code. The existing version 2.x source code will be completely re-written.
Design Objectives:
- Reference implementation – strictly adheres to the javax.comm API.
- Small footprint - Java and C code should strive to be as small as possible.
- Good performance – Java code should provide the shortest path possible to the native code. Native code should provide the shortest path possible to the underlying system.
- Fault tolerant - Java and C code should handle I/O errors gracefully, providing good error recovery.
- Proven – Java unit tests should achieve 100% code coverage.
- Compatible – the rewrite should be a drop-in replacement for the javax.comm library.
The rewrite was discussed in a mailing-list thread.
Milestones
To do...
What is left to be done and known issues
- Java Unit Tests
- Native code for MacOS X and Unix systems
Building the code
To do...