trurl works on urls ... what about URIs ?

[JimFuller-RedHat]

not trolling - just curious about opinions on this.

[bagder]

How do you define the difference?

[JimFuller-RedHat]

to take a more concrete use case, consider pURL (https://github.com/package-url/purl-spec)

> trurl pkg:bitbucket/birkenfeld/pygments-main@244fd47e07d1014f0aed9c

gives us

trurl note: Port number was not a decimal number between 0 and 65535 [pkg:bitbucket/birkenfeld/pygments-main@244fd47e07d1014f0aed9c]

[bagder]

URL/URI schemes that do not use :// are not supported by trurl because the libcurl URL API does not support those.

I don't think it is completely unthinkable that non-hierarchical schemes could be supported as well in a future, but doing that also opens up a can of worms do deal with.

[jacobmealey]

I don't think it is completely unthinkable that non-hierarchical schemes could be supported as well in a future, but doing that also opens up a can of worms do deal with.

This reminds me of a previous conversation had on a pr (#278) where pulling out the url API into its own library was suggested. That PR was focused around security and sandboxing, but I think this is a another potential use case.