Need feedback: Describe your use cases for non-HTTP(S) URIs
smola opened this issue · 5 comments
Galimatias born with the goal of parsing URLs that can be opened in a web browser. For my use cases, this included http, https and data. It soon became obvious that support for ftp, gopher, ws, wss and file would be sane and cheap to add since they are supported by most modern browsers and are specified in WHATWG's URL Standard.
Support for any other scheme is currently in place in a limited way. If there is double slash ("//") after the scheme (e.g. "git://"), the URL is parsed as a hierarchical URI. Otherwise, it is parsed an opaque URI. This is known to work with any URI except ed2k links (which is far from compliant with RFC 3986).
Before going on and overengineer anything, I would like to hear about your use cases with handling URIs other than http and https in Java. I will use this feedback to better define the scope of galimatias.
Thank you for your time!
Yes, please support git urls like:
- As used by github and gitlab:
git@github.com:smola/galimatias.git - As used by stash/ssh:
ssh://git@github.com/smola/galimatias.git
That would make this library more useful, for me atleast :)
ssh://git@github.com/smola/galimatias.gitwill be supported in galimatias 0.3.0, since it is now covered by the URL standard.git@github.com:smola/galimatias.gitmight be supported to some degree by a utility method in the future: #73
Could you add android-app to supported schemes?
A good use case is all the custom app schemes we need to use in Android apps to pass a normal URI but making sure only our app catches the scheme, like "my-app://homepage.com/path?param=1"
ws:// and wss:// for WebSockets are also useful (and they behave nicely, just like http://).