>URL syntax seems cleaner:
>
>unix://tmp/tcp/<pid>
>and
>inet://host:port/
true, but its redundant. inet hostnames cannot contain '/' so the
inet: prefix is completely unnecessary. look at the places where this
would actually be used:
1) host fork/execs GUI
you won't even see the form used, since its just
passed to the GUI as an argument to exec.
2) cmdline creation of GUI
would you rather use conventional r-cmd, ftp and other
inet syntax:
mygui -h foo.bar.com:33
or the syntax you show above?
--p
