Re: CGI Beginner -- WEB400

Hi Aaron,

CGIDEV2 does a good job of separating HTML from RPG.  And it's a valuable
tool.  But Justin appears to be looking for a green-screen alternative.  Do
you think that CGI is the right architecture to replace green-screens?

If so, I'd like to understand your reasoning.  And if not, I'd like to
understand that reasoning, too.

This is not an HTML vs. 5250 question.  Instead it's a question about CGI
architecture in general.  The API (even with the help of CGIDEV2).  The
interface with the HTTP server.  Performance.  Whether CGI would handle the
scope required of green-screen applications.

Thanks,

Nathan M. Andelin
www.relational-data.com



----- Original Message -----
From: "Bartell, Aaron L. (TC)" <ALBartell@taylorcorp.com>
To: <web400@midrange.com>
Sent: Tuesday, March 26, 2002 10:28 AM
Subject: RE: [WEB400] CGI Beginner


> >as well as fully working samples to download (cgidev2)
>
> I was skeptical about the CGIDEV2 stuff when I first started hearing about
> it, but then I used it.  IT IS GREAT!  It allows you to take all of the
HTML
> code out of your CGI program.  The way it works is you put your HTML in
the
> IFS(or member) and write out predefined pieces of HTML code.  So you may
> have a section of HTML code that looks like this:
>
> <AS400>head
> <HTML>
> <HEAD>Hi there /%custname%/</HEAD>
> <TITLE>TITle of the page</title>
>
> <AS400>body
> <body>
> </body>
>
> <AS400>end
> </html>
>
> Then in your CGI program you say . . .
>
> chain custno CSTMST;
> UpdHTMLVar('custname':CUSTNAME);
> WrtSection('head');
> WrtSection('body');
> WrtSection('end');
>
> . . .and the sections are written out to the browser with the customer
name
> replacing the /%custname%/ variable.  It has worked flawless for me so
far!
>
> Aaron Bartell

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.