Hi, What I would like to see if possible: 1. Session/cookie management 2. Easy way to generate the HTML DOM tree 3. Possibility of running as an apache module Here are some to compare to: http://www.gnu.org/software/cgicc/cgicc.html http://www.ii.uib.no/~stig/Projects/Cgipp/ Notice the cout << html() to output opening and closing tags etc. Also somewhat of interest: http://www.tntnet.org/ http://sourceforge.net/projects/mod-c Thanks Shams -- "Darren Garvey" <lists.drrngrvy@googlemail.com> wrote in message news:1be3e4b20704212220h63531907ld95fa9616d26d8cb@mail.gmail.com...
Hello all,
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 expansion.
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.
Regards, Darren _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost