>Provided examples look very much like https://github.com/michaelklishin/urly. Does e-f handle >relative resolution, parsing of broken (technically invalid) URLs?
Yes, it handles relative resolution, as well as normalizing paths: user> (normalize-path "http://www.test.net/some/uri/../path/./here?x=y&a=w";) "http://www.test.net/some/path/here?x=y&a=w"; user> (resolve-path "http://www.test.net/some/uri/../path/./here?x=y&a=w"; "new/path") "http://www.test.net/some/path/new/path?x=y&a=w"; user> (resolve-path "http://www.test.net/some/uri/../path/./here?x=y&a=w"; "/new/path") "http://www.test.net/new/path?x=y&a=w"; As for parsing broken URLs, that depends. URLs can be broken in a lot of ways, which means it's not clear how a broken URL should be parsed. It will allow technically invalid characters (which java.net.URI and URL will not), but doesn't go beyond that. I noticed that Urly will parse a URI such as "https://http://broken-cms.com"; as if it were "http://broken-cms.com";. Having this be automatic behavior when parsing makes me nervous. Maybe that "https" was important, and it should have been parsed as "https://broken-cms.com";. In some applications, it might make sense to have "https" always win. In others, like some sort of proxy, it might depend on the scheme of another URL, so you can keep the schemes of the URLs on either side in sync. Having functionality that allows you to deal with broken URLs is great, but having it be built into the URL parser seems dangerous. It's probably best to fail by default, so the programmer can determine the behavior they need for the broken cases as they come accross them. Also, it's good that you brought this up, because I just tried some things with Exploding Fish, and I need to add some better error checking :). On Monday, May 7, 2012 9:48:02 AM UTC-4, Michael Klishin wrote: -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
