3 ms·

There's a bit more info here: https://github.com/redox-os/redox/wiki/URL https://github.com/redox-os/redox/wiki/URL

• rch 11y ago
  Interesting. They mention 9P, but their approach reminds me of 1060's NetKernel: http://www.1060research.com/products/#roc http://www.1060research.com/products/#roc
• amelius 11y ago
  Very interesting. The only odd part is that the modules (drivers) themselves are not referenced by URL, but only by a simple word (in the example "port_io"). Also, I wonder how we could combine drivers. For example, (theoretically) instead of using "https" as driver, we could compose it as "HTTP over TLS over TCP", and change any of those subcomponents as desired. With URLs this might become clumsy.
  • XorNot 11y ago
    It depends how you want to express the hierarchy - URLs say "this is my transport system, and this is my address". But you could propose doing: tcp+tls+http://www.some.url/?options=here http://www.some.url/?options=here if you were okay with that. The problem creeps in when that tls fragment needs options and a path of it's own.
  • chei0aiV 11y ago
    Hurd translators can do that easily.