Dean, 2009/12/14 Dean Michael Berris <[email protected]>
> > > > `hello_world.cpp` can be repeated in `examples/server/hello_world.cpp` > > (where it can therefore be documented in quickbook). I think that's a > > really nice example, an HTTP server in C++ in less than 40 lines ;) > Though > > the `request_header` type is either a struct or it's using a C++0x > > initializer list. > > > > > Right. The request_header is definitely just a struct (or a POD). :) > I think it's not a POD because it contains members that are of type `std::string`. > > I'm still thinking about moving the request/response types as nested > types to the http::basic_client<...> and http::server<...> instead of > namespace-level types, or merging them to work for both the client and > the server. At the worst case I would make different specializations > based on the tag and type-defining them as different types > server_request/server_response at the namespace level. I find it a > little ugly in the C++ world of namespaces, but if you have other > ideas about making the naming convention more consistent I'm all ears. > :D > > Why have http::basic_client and not http::basic_server? I think nested classes could be a better approach, they will use the same tags as the server class anyway. Have a great day everyone, and Glyn please look forward to a Wiki page > on tags and descriptions soon. > Thanks, G
------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev
_______________________________________________ Cpp-netlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel
