> If such behaviour was to take form, there would be implementation left > (majorly) to web browsers. However, one identical point keeps coming up in > all and any proposal ive seen for this: Applications need a way to describe > what protocols they support. Most DEs have a vendor prefixed key for that. >
GNOME does not seem to have a key for that; not sure about other DEs. Afterwards, the content type has to be figured out. For http it's easy, for > say ssh not so much. Once you have a connection, you'll want to keep it > open. So ideally the same program handles the connection and the reading. > This conflicts with supporting arbitrary uris: you cannot know in advance > the mime type. > I came up with a solution in which the same program handles the connection and the reading. Moreover, "viewer" apps only have to deal with local files, so exporting the list of protocols supported by the app is not required. I've added it to the same document, it can be viewed at https://docs.google.com/document/d/1kfI-JB80egEmix0HIJkDkDtMHGF_xeQMqQANqIxxnlo/edit#heading=h.f9ujrurjty1j I'm looking forward to any feedback on this draft. -- Sergey "Shnatsel" Davidoff
_______________________________________________ xdg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xdg
