[cpp-netlib-devel] TODO's in http_integration

[Dean M. B. <mik...@gm...>]

Hi Guys,

As I've outlined in my latest commit (revision 60:
http://cpp-netlib.svn.sourceforge.net/viewvc/cpp-netlib?view=rev&revision=60)
I have a few items there that may need to be addressed somehow.

TODO:
- multi-line headers processing
- multi-part message posting
- change from multi-map to vector to preserve request header ordering?

With multi-line headers processing, I'm not sure if this is ever going
to be a problem with HTTP -- I'm not sure of the HTTP spec requires
that headers be a single line -- but I am a little worried about our
lack of HTTP headers checking. Does anybody have experience with
special headers that may span multiple lines? Or am I imagining things
here? :D

About multi-part message posting, I have not seen any documentation
regarding the semantics for a multi-part POST message. If it has
something to do with MIME, then that library has yet to be written
external to the HTTP implementation. AFAICT, each HTTP POST Message
has a single body, and a single Content-Length and Content-Type
headers -- If the actual body is a multi-part message, then I think
the body should have to be formed accordingly, and the Content-Type
correctly as well to something like 'multi-part/mixed;
boundary="some_boundary"'. The HTTP Client will then be sufficient in
its current form to be able to do:

  client_.put(request, "multi-part/mixed; boundary=\"some_boundary\"",
my_multipart_mime_body);

Another thing that may be required is to change the multi-map
underlying implementation for HTTP to use a list of std::pair<>'s to
preserve ordering. I've read something about the order of occurrence
and possible merging of repeating HTTP Headers.

One last thing which needs some scrutiny: maybe we should define a
User-Agent: header to identify cpp-netlib? :D

Thanks for the time (if you get this far) and let me know what you think! :)

-- 
Dean Michael C. Berris
Software Engineer, Friendster, Inc.