Re: I-D ACTION:draft-ietf-http-ses-ext-01.txt

> 
> 
>    I would like to suggest a couple of things for the persistent 
> session spec: 
> 
>    1) A specification for a CGI variable that would indicate 
> to a CGI program that a session is persistent. Perhaps called 
> SERVER_CONNECTION it would have the content of the *server's* 
> Connection: header for the last transaction. Using this with the 
> HTTP_CONNECTION variable would allow a CGI program to determine 
> if it's dealing with a persistent connection. 
> 
>    This information would be useful for CGI state management. 

I would support this part of the proposal.  I've had even more obvious example,
a CGI that generates pictures based on defined commands and a table of
such generated pictures.  Overhead of establishing connections and
launching CGI is simply unbearable (even more when you take into account
that it is something like 8 generated pictures less than 200 bytes each).

Example is on:

<URL: http://www.rasip.fer.hr/~tm/gluck-simul.html>

> 
>    2) A method for a CGI program to originate request for a 
> persistent connection. Simply make the protocol bi-directional. 
> If the server originates a "Connection: persist" to the client, 
> the client may respond back with "Connection: persist" and the 
> exchanges could continue as already specified. 
> 
> 
> +--------------------------------------------------------------------------+
> | BearHeart / Bill Weinman | BearHeart@bearnet.com | http://www.bearnet.com/ 
> | Author of The CGI Book -- http://www.bearnet.com/cgibook/ 
> 
> 


-- 
    | Mirsad Todorovac					|
    | Faculty of Electrical Engineering and Computing	|
    | University of Zagreb				|
    | Unska 3, Zagreb, Croatia 10000			|
    |							|
    | e-mail: mirsad.todorovac@fer.hr			|