There are many ways to approach these issues.  I have had success tracking
state by using the methodology I shared in the last few Interex Enterprise
Solutions issues.

Instead of running a completely new process each time Apache receives a
request, I funnel the request into a running program (written in the
language of your choice).  This listening process has a stable of worker
(son) processes so that it can devote itself to dealing with incoming web
requests.  When a response html page is sent to the web client by a worker,
it contains the worker's ID in a special hidden field.  When the client
responds the listening process sees the ID and routes the request
accordingly.  The worker process knows where the client was and can deal
with the new screen.  To conserve workers, you may want to time out your
web client after an appropriate interval.

Also, to reduce the typing, an html page may be used as a template for all
the iterations of a given screen.

Regards,

Frank Gribbin
Potter Anderson & Corroon LLP

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *