Stewart Stremler wrote:
Named pipe, cat, and tee?
hmmmm...
Subclass the stream classes to record off the bytes sent through them,
a sort of java-level "tee" program.
Streams are nice that way.
Except that the code does not use stream classes.
The Comm API does not provide enough control over the serial ports (Comm uses streams).
Further, Sun's Comm API has crappy performance and does not work worth a damned on Windows
or Linux for this application (Note: Only IBM has a comm.jar package for Linux. Sun has
thus far been too lame to support Linux directly, and instead rely upon a third party
implementation of their Comm API for non-windows and non-Solaris platforms.). I purchased
the SerialPort API from Serialio.com. Even though SerialPort has a Comm API, it also has
Serialio API that provides more control over the serial ports (e.g. - the ability to set
Tx and Rx timeouts), has better performance, and fixes some bugs that Sun will not fix in
thiner Comm API. Using the Serialio API, they don't use streams but instead use methods
such as Serialio.putData() and Serialio.getData().
Could this be sub-classed to provide what I need? Maybe.
PGA
--
Paul G. Allen
Owner, Sr. Engineer, BSIT/SE
Random Logic Consulting Services
www.randomlogic.com
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
