Re: Java Applet pulled from VMS Web Server

Hi Arne,

I think this is what many consider limited. Probably not a problem
for you because you want to do thing serverside anyway.

Apart from Request-initiation, Remote-task coordination, and Presentation,
what else is there?

AJAX uses JavaScript not Java.

JavaScript and Java does not have much in common except 4 letters
in the name ...

Are you saying that the Interfaces to the Socket Methods contained in the
Java Applet JAR file are not "surfaced" by AJAX?

(I can't believe I just wrote that ***! It scares me even more to think
that the terminology could be correct :-)

Look Arne, this is what I see happening: -

1) HTML page has an Applet tag so that, when the page is displayed, the
Initialization method gets activated
2) In the initialization, I choose to
2a) Created a socket and connect back to the VMS server that is hosting the
applet (but different than the UNIX server hosting the html page)
2b) Ask for VMS username/password and send them to the Tier3 Application
Server on that node
2c) Recv the authorization success/fail
3) A seperate AJAX thread in my browser is monitoring the state of the
Employee Name field and for every non-deterministic change I will Send a
"Lookup mf_personnel.employees message" to the server and refresh
"blink-free" the drop down under the name.
4) When the browser is closed, the destroy method for the applet closes the
socket

Alles klar?

Are you really saying that Javascript is incapable of accessing any of the
input/output streams that have been opened by the Applet?

AJAX is completely different from Java applets.

AJAX uses traditional web frontend technologies: JavaScript, HTML, CSS.

Java is a real programming language.

There are security rules for JavaScript also, but the rules are much
less well defined.

Arne, you keep painting an either/or picture. Is it really that clear-cut?
Can Javascript really not call/evoke/incantation Java
applets/methods/procedures?

Cheers Richard Maher

"Arne Vajhøj" <arne@xxxxxxxxxx> wrote in message
news:4545300c$0$49203$14726298@xxxxxxxxxxxxxxxxxx
Richard Maher wrote:
Applets sit at the client end (browser) and can't usually do very much
because of security concerns.

It is my understanding that it is a common and secure practice to have
your
browser settings organized to let unsigned applets run in the sandbox
and
connect back to the server that they were downloaded from. Are you
saying
this is not the case?

I think this is what many consider limited. Probably not a problem
for you because you want to do thing serverside anyway.

As far as Applets not being able to do "much" I've had some very useful
exchanges with people doing extremely interesting things with Java! For
example, using my Mickey Mouse employee surname lookup from the
mf_personnel
database people have described to me how they are using AJAX to monitor
the
input field and for every keystroke send the updated contents back to
the
server for a new list of matching employee surnames and display it as a
drop-down as the user is typing in. Similar to what Google does with
search
strings if you know what I mean.

Hmm.

AJAX uses JavaScript not Java.

JavaScript and Java does not have much in common except 4 letters
in the name ...

Now, because no one seems to speak english in the Unix, Java, New world,
I
have additional questions such as: - Is the "Asynch" part in AJAX
different
to the other sperate "threaded" examples people have shown me? Are any
reduce security settings required for AJAX as opposed to other
Javascript?
Is it available everywhere normal Javascript is available?

Asynch in in AJAX just means that the browser can refresh part of a page
instead of the entire page ("blink free").

AJAX is completely different from Java applets.

AJAX uses traditional web frontend technologies: JavaScript, HTML, CSS.

Java is a real programming language.

There are security rules for JavaScript also, but the rules are much
less well defined.

Arne


.