Aaron Bartell wrote:
Nathan, how do you do it from your end?
I oppose the idea of delineating program flow in a configuration file with a tag language like XML.
Under my interface, browsers send requests to servers with the following syntax:
post.shtml
where ".shtml" tells the http server to forward the request to the application and "post" is the requested "action".
The RPG program responsible for handling the "action" has a "select" block:
select;
when rw.action = "POST"
...
when rw.action = "DISPLAY"
...
when re.action = "???"
...
endsl;
It's pretty typical for a programs to handle 8-10 "actions". And an action may output one page under one condition and another page under another condition.
Under my interface, browsers don't request "pages". They request "actions". The program decides which "page" to generate.
Of course, with AJAX, the response might not even be a "page".
Nathan.
As an Amazon Associate we earn from qualifying purchases.
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.