Re: Did anyone attend the Webfacing lab at COMMON?

G'day Nathan,

I think performance is a key issue with any Internet application - "Your
competition is just one click away!". But as stated in my original e-mail
about the sample applications to those people registered on my newsletter
mailing list - the samples are not to demonstrate the speed of WEB:2E. A
serious web server should be capable of supporting 100's if not 1000's of
concurrent requests - the Model 150 cannot do this.

I should mention that the splash screen for each of the applications was
inserted to give the AS/400 enough time to launch the application due to
performance issues. On a larger server I would not use splash screens for
the applications because I would expect the server to react in a more
timely manner.

I had purposely configured WEB:2E to present the model dialog box to report
the error so that when the box was closed the web page then reverted back
to the start page. Out of the box it does not show the modal message box
and does not revert back to the start page.

The applications are running standard COOL:2E functions with little or no
changes to default behaviour. Selecting multiple subfile selections and
pressing enter will cycle through all of the selections - even if [Exit] is
pressed while viewing one of the selections. In hindsight I should have
used a template that supports [Exit] in a more favourable manner. This is
not an issue with WEB:2E but the design of the functional flow of the
application - easily fixed using the COOL:2E action diagram editor.

The big plus for WEB:2E is that it works straight out of the box. I
installed the runtime on a client AS/400 on the weekend to demonstrate the
capability of WEB:2E and it worked first time without any modifications and
after about 30 minutes install time. Nice to know you can be on the web in
such a short period of time.

Regards,

Darryl MILLINGTON
HawkBridge Pty Ltd (Australia)
http://www.HawkBridge.com
AS/400 Products and Services