Hi guys, It's been a while since you've heard from me, and first of all -though somewhat late- a Happy New Year. I've been reading up on the RFC and Spirit documentation (Spirit is pure genius by the way). I'm now working towards a full RFC compatible parser[1]. In doing so I've found the newer RFC3986 is much more of a pleasure to work with, and the specific HTTP parser isn't needed any more.
I've noticed a couple of things though, and I'm uncertain on how to solve them. First of all, ports, there is the difference between the parsed port, and the actual port to use when connecting, based on default ports. The google-url has a port and EffectiveIntPort function, but this information is also needed when normalising the URI. Secondly, the parser knows the difference between no fragment, and an empty fragment, but the current API does not expose this. Would exposing the optional<string_type>'s be a solution? Jeroen Habraken [1] This is currently not committed to git yet, I have still to properly figure out GitHub, and fork the right branch ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Cpp-netlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel
