|
> From: "David Morris" <David.Morris@plumcreek.com> > Your assumption that all connections are via TCP/IP is > incorrect. If you use the native drivers, you will bypass > the overhead associated with TCP/IP. My understanding of the use of sockets to interface with native resources was based on reading. Not completely assumption ;-) If os/400 Java and native components are not communicating via sockets, then what? Memory pointers? By "native drivers" are you referring to the record level access support provided in the iSeries Toolkit? > Some things I would say are an advantage on the iSeries > other than reliability... I'd like to understand the reliability issue better. It seems that an integrated xSeries server would be quite reliable (from a hardware perspective). But I wonder about the reliability of the JVM under Windows or Linux. One way to destabilize Windows is to concurrently run a lot of different software (executables, DLLs, and activeX controls). But that's not the same as concurrently running a lot of classes within a single JVM. In one case the OS is managing (trying to, anyway) the workload. In the other case the JVM is managing the workload. Is the OS/400 JVM more stable than one running under Windows or Linux? > ability to set priorities for jobs and threads > the ability to associate individual users with a task. Is that important if you're just running Servlets, JSPs, and Beans under Tomcat? Thanks for your reply, Nathan M. Andelin www.relational-data.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.