I'd fall back to using apache or lighthttpd anytime. However module support would be cool. I mean design the library in such a way that it could run as a standalone cgi program or as an apache module like php. Thanks Shams -- "Darren Garvey" <lists.drrngrvy@googlemail.com> wrote in message news:1be3e4b20704251546l79e1036u99fb51c9f67274d0@mail.gmail.com...
On 25/04/07, Jose <jmalv04@gmail.com> wrote:
The numbers refer to the use cases:
1) CGI output support 2) FCGI deamon support
Both included.
(and optionally FCGI on the c++ web server side to
interface to the FCGI daemon)
My guess is that if this is ever done, it won't appear for a long time.
3) an improved asio http server that supports CGI pages (this would be very
useful)
Adding http support to the library is a possibility, and has been discussed before. It's _not_ part of the SoC project though: at best it'll be added later, assuming all goes well. That said, http support isn't likely to be safe for use as a public 'server' at any point: that's a huge task and one probably far beyond the realm of any single library.
4) advanced applications, like debugging
Not included, but see my previous mail.
Darren _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost