Re: Non Java based replacement for Client Access -- MIDRANGE-L

Subject: Re: Non Java based replacement for Client Access
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Tue, 18 Jun 2019 10:27:26 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Tue, Jun 18, 2019 at 10:11 AM John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

The JRE would still run on the workstation ... it just wouldn't be stored
there.

The question is: How would this work? Surely *something* has to be
running locally. If not JVM, then at minimum some kind of
communication. So now we're either talking about a browser or some
other non-Java local client.

The JVM would be running on the workstation ... just stored on a network
share.

Instead of using "C:\Program Files\Java\jrex.x.x\bin\java.exe"
They would use "M:\IbmAcs\jre\bin\java.exe"

Where M is a mapped network drive.

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Non Java based replacement for Client Access , John Yeung

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.