Welcome, Guest
Please Login or Register.    Lost Password?

Java client under Windows and Linux client issues
(1 viewing) (1) Guest
Go to bottomPage: 1
TOPIC: Java client under Windows and Linux client issues
#304
Java client under Windows and Linux client issues 13 Years, 6 Months ago Karma: 0
1 I tried the Java client under Windows and it clearly doesn't perform as well as the native Windows client - which apart from the PATH issue I mentioned elsewhere (it sets the path so anyonce can read the logs for example) is pretty well perfect.

The Java client downloaded 1.3.1 run time environment which clashes with other RTEs - principally 1.4.1 required by DELL Remote Access. Should you not be updating to a later version anyway?

2 I also tried the Unix client on Unix (RH Linux 7.3, XWindows 3.6 I think) and it is much slower to respond than the Windows client and there were also so painting problems - when I moved the windows some bits were not all moved. For Unix clients, the clear recommendation would be to use a native X server on the client's machine. Is there any prospect of the Unix server coming up to the Windows performance or does it improve on X-4?
Loggy
Fresh Boarder
Posts: 9
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#307
Re: Java client under Windows and Linux client issues 13 Years, 6 Months ago Karma: 2
1 I tried the Java client under Windows and it clearly doesn't perform as well as the native Windows client - which apart from the PATH issue I mentioned elsewhere (it sets the path so anyonce can read the logs for example) is pretty well perfect.

Just for the record, who can read the logs is a function of who has permissions in the system to access those directories and files. The "PATH" environment variable does not have any effect on this.

The Java client downloaded 1.3.1 run time environment which clashes with other RTEs - principally 1.4.1 required by DELL Remote Access. Should you not be updating to a later version anyway?

We release updates as we test and certify the client for use on different JVMs. The process is ongoing, of course. We also expect that if you want to change the HTML pages to reference the later JVM version, you are always able to do that.

2 I also tried the Unix client on Unix (RH Linux 7.3, XWindows 3.6 I think) and it is much slower to respond than the Windows client and there were also so painting problems - when I moved the windows some bits were not all moved. For Unix clients, the clear recommendation would be to use a native X server on the client's machine. Is there any prospect of the Unix server coming up to the Windows performance or does it improve on X-4?

It is our goal to get the native X11 client (which is what I think you meant here) functioning at a level as close as possible to that of the native Windows client.

Troy
troy
Administrator
Posts: 231
graphgraph
User Offline Click here to see the profile of this user
Gender: Male Birthday: 01/14
The administrator has disabled public write access.
 
#309
Re: Java client under Windows and Linux client issues 13 Years, 6 Months ago Karma: 0
Troy

Thanks for the info on JVMs and your aspirations on the X11 client. This I look forward to, although the licence model will encourage me to suggest to users that they use native X.

A few more questions:

In the licence system, does it check whether the same person initiates more than one client or would that cost 2 seats?

If I were running a Windows host as well as Linux host, are the licences served by a common server or would I need two licence servers?

One the PATH issue, while you are obviously right that it is the permissions that control access rather than the path, I have to point out that in the standard, un-Bastilled RH8 on which GG is running, /var/log/* is owned by root with 0600 access.

I would have thought that, particularly as GG is about external access, the permissions for most if not all of the files in the etc directory should also be 0600 by default.

I still believe that the X initialising script is mis-handling the PATH environment variable, which should be

/usr/local/graphon/bin:$PATH

In a production environment, serious hardening is required.

Thanks for your responses.

John
Loggy
Fresh Boarder
Posts: 9
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
Go to topPage: 1
Moderators: troy, Andyl