×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: "Dean, Robert"
An apples-to-apples comparison would be, for example, a Java program that uses
an HTTP client to consume the CGI program results and JDBC to consume an SQL
result set.
That would be a good test. One difference I see between a CGI interface and a ODBC/JDBC/QZDASOINIT interface is that the CGI interface returns the entire result set to the client all at once, while the ODBC/QZDASOINIT interfaces I've been testing with return a small subset of the query results, then waits for the client to request more. QZDASOINIT behaves more like a tunnel. The complete SQL result set remains cached in the QZDASOINIT job until the client requests it. In the case of IBM i Navigator and Visual Foxpro clients, it may take a minute or more to retrieve the entire result set for "display" on the client. But that appears to be controlled by the client.
-Nathan.
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.
midrange.com
