^ASP

One of the most difficult things to get use to in ASP is the ability to use one file (ASP program) for many purposes. At first glance this may seem strange in the context of reuse but consider how the web has progressed. The first implementation of web servers typically kept the form display (HTML) separate from the form processing (CGI/perl). Now it makes some sense to keep everything together in one place (form, scripts, etc).

The following events could occur for a form:

n Page Open – no additional data (simple URL) --> display whatever is needed to collect or process form

n Page Open – with preset data (URL with parameters) --> eval the parameters and then display the results

n Form Post – Form completed and sent to posting URL --> eval form fields and then display (any page could contain more than one form)

^{Display Architecture}

An important aspect of any demonstration is visual appeal. One goal was to add attractiveness in LINX with a minimum effort yet with flexibility. The typical framework was used so that consistent content could appear across pages while providing a sizable area for the variable content.

Basic web page design places each of the display components into a table with some sizing parameters. An additional restriction was added to be able to individually modify the components using any HTML editor without having to do any special programming for each change.

The display architecture was improved by creating a subroutine that pulls display content from files. This was then used to add components into the table framework as needed.

Add description and code for Function ResponseBody