Diese Seite mit anderen teilen ...

Informationen zum Thema:
Forum:
JAPI Forum
Beiträge im Thema:
2
Erster Beitrag:
vor 16 Jahren, 1 Monat
Letzter Beitrag:
vor 16 Jahren, 1 Monat
Beteiligte Autoren:
Merten, C. Kleffner

several questions

Startbeitrag von C. Kleffner am 06.06.2001 16:27

Hello,

I was able to run the demos via http on a hpux workstation with Windows NT as a DISPLAY server. 'japi.jar' was compiled with the JDK on the HP and transfered to Windows and started there on JRE 1.1. 'japi.jar' seems to be portable across platforms (as one would expect).
It would be helpful to to copy 'japi.jar' to the download area. This would prevent at least most people to download the complete source tree just to compile the java sources.

Questions:

1) on HP I compiled several C-soures and even suceeded there with the sources in the mingw distro which seems to be different in some details (function definitions) to other tarballs. Maybe this updated sources should be standard for other unix compilers?

2) How many connections can I open to the japi process?

3) What about security issues?

4) What about license: LGPL already?

Sincerly yours

Carl

Antworten:

Hi,

> It would be helpful to to copy 'japi.jar' to the download area.
> This would prevent at least most people to download the
> complete source tree just to compile the java sources.

There is a easier way to start the JAPI kernel. Write a program with the following statements:

begin prog
j_start();
j_quit();
end prog

and put the executable in your autostart folder. Then, the japi kernel is started every time you log in. But, of course, i will put the jar File to the download section.

> 1) on HP I compiled several C-soures and even suceeded
> there with the sources in the mingw distro which seems to be
> different in some details (function definitions) to other tarballs.
> Maybe this updated sources should be standard for other unix
> compilers?

There is no difference between all gcc based sources. (linux, solaris, cygwin, mingw for gcc and g77). So, these files seemed to be the best start to all other UNIX Platforms. If you do some patches to compile japi on HP, please send me the patches.

2) How many connections can I open to the japi process?

The JAPI-Kernel is implemented as a multithreaded damon. So, there are no connection limits, except memory and CPU speed limits.

3) What about security issues?

because of no restrictions, everybody outside could connect to a running japi kernel. This is a security hole, which maybe will be solved in the future. The japi kernel itself makes no disk access, (exept the filedialog function). So, nobody else should be able to read or write to your disk, using a running japi kernel. JAPI can be compared with the X-Server on unix-Systems.

JAPI is Open Source, so if you are in doubt, have a look at the JAVA sources.

4) What about license: LGPL already?
Yes, JAPI is set to the LGPL. I will a add licence link soon!

Hope this helps

Merten Joost

von Merten - am 07.06.2001 13:05
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.