From: Darren Garvey (lists.drrngrvy_at_[hidden])
Date: 2007-04-22 01:20:35
In preparation for working on a cgi library for the Summer of Code
(proposal: cgi.sf.net/proposal.html), I'd like to collect a list of
use-cases for such a library.
The purpose of this discussion isn't to decide what goes into the library
(the scope will be limited to CGI, FastCGI and possibly SCGI backends) -
although please don't let that censor your thoughts - but to ensure the
library is structured in such a way to allow the widest potential for
Of particular interest are thoughts about:
- CGI vs. HTTP: if the library worked with (for example) mod_proxy_http,
would the 'limitation' of only providing CGI variables be an acceptable
compromise for the sake of portability across protocols?
- how significant SCGI is (would anyone use it?);
- non-CGI/FastCGI/SCGI/HTTP protocols that might be of interest;
- low-level design decisions
There's going to be a lot of work put into this library over the Summer, so
now is the best time to impress your ideas on us, before they're 'set in
stone', so to speak.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk