Re: [cpp-netlib-devel] Some code already up in subversion

[Christian H. <chh...@gm...>]

On 21 May 2007 20:02:02 +0200, Peter Simons <si...@cr...> wrote:
> Hi Dean,
>
>  > I agree that boost/network/rfc2822 doesn't feel natural.
>  > Would you have a different name from rfc2822 which might
>  > make more sense and be more descriptive?
>
> No, I think rfc2822 is a perfect name for that hierarchy. My
> problem is with the "network" part, because the code is about
> text parsing, not about networks. The location I'd prefer
> would be more along the lines of "boost/spirit/rfc2822",
> "boost/parsers/rfc2822", or even "/boost/ietf/rfc/2822/".
> Whatever. The point is that putting this code into a network
> hierarchy doesn't feel right, which is why I suggested a
> different organization that offers more granularity.

For the time being we can just add them to "/boost/ietf/rfc/2822/". I
think that would make to most sense. More important is to get the
software design right.

>  > [scope of boost.network]
>
> Alright, thank you for sharing your ideas. From what I can
> tell, the things we ought to develop in this project are
> general purpose HTTP and SMTP drivers that can be re-used in
> clients and servers. I have implemented a (very rough) HTTP
> server here:
>
>   http://git.cryp.to/?p=mini-httpd
>
> I would very much appreciate feedback concerning that daemon,
> by the way. The latest "snapshot" comes with a
> Autoconf/Automake build system that should -- in theory --
> work on most Unix machines. My understanding is, however, that
> there is at least one more project (libhttpd?) that tries to
> do the same thing.

Another very basic implementation is provided by asio.

http://asio.sourceforge.net/boost_asio_0_3_7/libs/asio/doc/examples/index.html

But there is also a next version in the cvs trunk:

http://asio.cvs.sourceforge.net/asio/asio/src/examples/http/server2/

How would you guess to envision the handling of the status codes and
the request methods like GET, POST, etc. For the status codes I would
not vote for enums. I think small structs should encode them.

Christian