Hi Guys,
These two features weren't as hard to implement as I thought, so I
went ahead and committed revision 83 which includes caching the
resolved endpoints, and handling 300..307 redirects from the server.
I also moved the uri parsing functionality into its own method from
http/impl/request.hpp still part of the http::request class. Next
steps should be to move it out completely and into the
network/utils/uri/ directory. I believe someone else has mentioned
that they already have an implementation that they want to make part
of the library -- should we do that anytime soon?
If not I can start collecting utility functions and move those into
network/utils/... -- the only thing I can think of right now are the
URI parsing functions, but I guess there's more that can be factored
out and made into utilities.
HTH
--
Dean Michael C. Berris
Software Engineer, Friendster, Inc.
|
