Iostream functionality.

Streamed IO, likely to be similar to Boost.Asio's basic_socket_stream<> would be nice, although .

SCGI support.

I haven't managed to get apache/lighttpd configured properly for SCGI, so this isn't functional yet.

FastCGI client support.

FastCGI is supported in server-side applications. Support for client-side applications would be useful.

FastCGI support.

I would like to add to the FastCGI functionality on Windows, where currently only anonymous pipes are supported. It is possible to customise the library to use external FastCGI apps, but this is not documented.

Access to error output streams

CGI, SCGI and FastCGI all make provisions for some sort of error outputting, according to the following table:

Even though the server is not obliged to do anything with this output, it is generally dumped into the default server error log. This can be invaluable for debugging.

Access to the above streams will be implemented as a Service, which can be switched on or off at runtime. Output can be sent either to stdout, stderr, or both simultaneously. If this isn't enough, a user can add their own custom service layer, which can manipulate the data as it is read/written in any way they wish (such as logging to a database, url-encoding/filtering data, or playing an April Fool's prank on your website visitors).

Concept Documentation

Even though this library introduces very few new concepts, they are not currently documented. Links to Boost.Asio's concept documentation is also required (essentially as part of a reworking of the doxygen reference section).

Unicode Support

The library currently makes no documented provisions for Internationalisation support. The string type used in the library is templated but this is as far as support goes. A Boost.Unicode library would help a lot with adding this support. Comments on this topic by domain experts are most welcome.