Reece Dunn said: > Beman Dawes wrote: > >>I gave that some consideration at one time, but the full URI spec >> (http://www.ietf.org/rfc/rfc2396.txt) covers so much that is totally >> outside the scope of a filesystem library that it really seems an >> over-generalization to try to included it as part of filesystem::path. >> The tail would soon be wagging the dog:-) > > I was not suggesting that URL handling was a part of the file system > library. What I was considering was a URL library with a *bridge* to the > file system library, e.g. (I may have the names wrong): > > boost::url::url localsite( "http://localhost/xml/docs/overview.xml"; > ); > > // use native OS interface: > boost::path localpath1 = boost::url::getpath( localsite );
This mapping can't be easily done. Where this maps to is basically known only to the web server. A mapping from a "file://xml/docs/overview.xml" URI would be useful, however. It should also be fairly trivial. -- William E. Kempf _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
