Implementations
Rendezvous Java language interface offers several implementations. Implementations summarizes and compares them. To specify an implementation, see Archive Files and Tibrv.open().
Aspect |
JNI (Native) |
JNI (Native) |
Suggested Usage |
Use in most situations. |
Use only for backward compatibility, when it is impractical to migrate to the JNI preferred implementation. |
Coding |
A thin Java layer serves as a programming interface to an underlying C implementation. |
|
Primary Runtime Environment |
Independent application |
Independent application or browser applet |
Scope of Functionality |
Maximal coverage of C functionality. |
|
Speed |
Faster for all receiving applications—whether they access all fields or only a small subset of fields from inbound messages. |
Slower for all receiving applications. Retained for backward compatibility only. |
Transport Support |
|
|
Message Storage |
Messages exist both in Java (garbage-collected) storage and in native C (JNI) storage. |
|
Timer Granularity |
Supports fine-resolution timers (within operating system limitations) |
|
Forward Feature Support |
In release 8.0 and later, only this implementation supports new features; for example, sending message arrays, vector listeners, dispose. |
None |
Library Requirements |
Must load the Rendezvous JNI library |