Re: OS/400 command set

I believe that persistence is possible in HTTP. There is persistent CGI,
net.data has a persistent flavor. So the state can be preserved on the
server, IIRC. But then a new server has to be started to handle it, and it
won't end, or allow another IP address to be server.

Vern

At 09:17 AM 11/14/2002 -0600, you wrote:

-snip-

What you are thinking of is that it's "stateless".  Each file that you
request is it's own request, unrelated to all others.  This mainly makes
sense when working with CGI scripts or similar "program-driven" requests.
You send variables to the web server, and it sends back data.   That's
considered the entire life of the transaction.   When you need to request
the "next screen" of information, it's a whole new "unrelated" request.
The server calls teh CGI program again, as a new program call.  You can
use a variable embedded in the web page to try to keep track of where you
left off, but all of the data has to be saved from request to request,
since (from the HTTP server's perspective) each request is unrelated.

-snip-