J
Jeffrey H. Coffield
Arne said:Jeffrey H. Coffield wrote:
The JNI solution is not needed for client Java - it would be needed
for server Java.
Arne
Even if the Java app runs on OpenVMS, which we have a couple, we use the
same connection logic so we don't have two different methods for Java.
One for OpenVMS and one for everything else. A simple benchmark did not
show a significant difference between using TCP/IP on the same node as
using JNI. I suspect that most of the load is generated in converting
data to and from the OpenVMS native format to what Java wants which is
needed in both cases.
We actually have two different connection methods now. One uses a
TCPI/IP service so you get one persistant connection per Java client
(like FTP or Telnet). This allows for the server to send data to the
client in real time and is more compatible with traditional OpenVMS
locking. The other is based on a HTTP post with an XML response. This
requires the whole session management logic but this allows the same
back end logic to be used with either a Java/Swing/WebStart front end or
HTML/Ajax/Jquery.
Jeff
Jeff