Re: Another option (was Re: AJAJS - thin client web app using mainly XMLHTTPRequest and eval())

On Sep 29, 7:42 pm, "Richard Maher" <maher...@xxxxxxxxxxxxxxxxxx>
wrote:
Hi David,


[snip]


I agree with all of the above but to be fair to the OP hasn't technology
such as AJAX, in some ways, turned the clock back and created a hybrid by
merging the web and client/server paradigms? There are people, certainly
within this group, who'll contend that if it doesn't have a SUBMIT button
then it's not a browser application. Others, myself

I'm not sure I follow, but a form without a submit button is a bad
idea.

included, can see
browsers as the run-time environment for a genre of "new" lightweight
client/server applications.

Yes, but light is relative. The OP proposal is too light, wasting the
capabilities of the browser and PC.


Anyway FWIW here is how I'd do it (HTTP is great for serving up web-pages
and images, but is it really the best tool in the box for a secure,
high-performance, middleware communications back-bone? The browser *is* the
GUI, but is a Web-Server really an Application Server?)

The Web server is just a conveyance between the presentation and
middleware layers.


http://manson.vistech.net/t3$examples/demo_client_web.html


That didn't work too hot for me in IE7. I got a message saying the
Java runtime environment couldn't be loaded (and little else.) I
don't think your app caused the error, but it didn't recover from it
very gracefully. In other words, it degraded to a virtually blank and
unusable page.

All of the HTML, Javascript, and Java Applet sources can be viewed at: -

http://manson.vistech.net/t3$examples/

To see the example sucessfully you will need:-

1) Javascript enabled

Check.

2) Java Applets enabled

Check.

3) Can't be behind a Firewall that forbids all unknown outgoing connections

Check.

(otherwise open-up 5255)
4) Must be running SUN's JRE 1.4.2_13 or later (1.6 is advised)

No idea.

5) Must be running Internet Explorer (6 or later) or Firefox (Haven't tested
other browsers) I'm told it works with Safari Version 2.0.4 (419.3) Java
Plug-in 1.5.0 Using JRE version 1.5.0_07 Java HotSpot(TM) Client VM.

All things being equal you should then be prompted (via Java modal dialogue
box) for:-

Username: TIER3_DEMO
Password: QUEUE

Never got this far.


Here's some of the functionality-catwalk highlights from the example: -

1) Full, one-time, context-specific, VMS User Authentication. No Cookies,
Session IDs, Password Caching or generic Work-Station or Browser
credentials! When you load the demo_client_web.html page into your browser,
a Java Applet is automatically activated that prompts the user for their VMS
Username and Password via a modal dialogue box. If authorization fails, the
"Access Denied" page will be displayed and VMS Intrusion Detection (in
accordance with the policy set out by your System Manager) will be enforced,
and Login-Failures is incremented in SYSUAF. Alternatively, if authorization
is successful (and you left the "Display Logon Confirmation" box ticked)
then a Welcome dialog box will be displayed detailing last login times and
the number of unsuccessful login attempts (if any). Login-Failures is now
set to zero and last non-interactive login time is set to the current time.

If you refresh this page, or move to a different page, then the server
connection is broken and you must be re-authorised before continuing to
access the Demo Queue Manager application.

Right. I take it it's one application per page.

[snip]

Clearly Ajax isn't appropriate this application, so Java is required.
But what sort of practical Web application would you build with this?
I guess it would make sense if you need remote access to a mainframe.


Regards Richard Maher

PS. The server code can be in any 3GL but, for this example, I chose COBOL;

Since I didn't see the example, I really can't comment on it, other
than to say that COBOL is an odd choice.

Thanks for sharing.

.

Quantcast