This content has been marked as final. Show 5 replies
Java comm would be closest I would suppose.1 person found this helpful
Thanks for the reply. Looking at the Java.comm I will want to make that my eventual interface to the serial driver. When I look at the CommDriver's initialize() function, it is during that method call that any required Native Libraries are loaded.
So what I was hoping to find out about was a standard or common practice that applies to the code that lies between the 8 driver interfaces and the CommDriver subclass and CommPort subclass.
If you're going to write a JNI shim between Java and the driver, it will end up being a .so or .dll that is loaded into the JVM using System.loadLibrary()1 person found this helpful
Both Windows and Linux .dll and .so files have a mechanism to provide initialisation and teardown of the .dll/so. So you could put the install/uninstall calls in there.
Hope this helps
870745 wrote:As applies to java.comm?
So what I was hoping to find out about was a standard or common practice that applies to the code ...
I doubt there is such a thing. There just are not that many implementations. And most are proprietary so they are not saying.
You can look at rxtx (java comm api) and download the reference implementation and see which ways they do it. If they both do it one way that might be good. If they do it different ways then neither means much.
Thanks to both of you for the help. I'll look into how they do it.