From: Jose (jmalv04_at_[hidden])
Date: 2007-04-23 08:52:17
The project should make it clear how it supports different needs and it
allows a basic to advanced path:
CGI: support to allow any c++ program to output results to a browser
(typical cases are to output a html or an image via a web server)
FCGI,SCGI: support to build a server deamon that interfaces to a web
server via tcp sockets (e.g. apache front-end via mod_fcgi to a custom c++
Web server: support to build a basic web server tied to a c++ application
but with the web server also supporting CGI/FCGI on the server-side (e.g.
improved asio http server)
Advanced - simulations, debugging: support to build a web server thread
that can be used to debug the application or to query the status of a long
running application via a web
As for the other features (sessions, templates, ..) I think the first
priority should be sessions but probably this is already too much for this
I am glad this project got accepted and also that Chris is mentoring it, as
there is a lot of related work already in asio examples.
On 4/23/07, Shams <shams_at_[hidden]> wrote:
> Yes I forgot to mention that and IF possible I'd rather go with a
> system but as a separate library or project.
> Here is an example of a c++ template language from Google.
> "Steven Siloti" <ssiloti_at_[hidden]> wrote in message
> > Shams wrote:
> >> 2. Easy way to generate the HTML DOM tree
> > This seems to be a commonly requested feature form cgi libraries but is
> > it really that necessary? It seems to me that it just encourages bad
> > habits, i.e. mixing logic and presentation. Shouldn't we instead focus
> > on providing a convenient template system a la ctemplate but with a more
> > appropriate API?
> > Steven Siloti
> > _______________________________________________
> > Unsubscribe & other changes:
> > http://lists.boost.org/mailman/listinfo.cgi/boost
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk