What are the long term plans for interfacing between the browser and the safe net?
Obviously, we currently have the proxy, which is HTTP/1.x based. Considering all requests will go through the same proxy/launcher, HTTP/2 would be a big win, as it could all be multiplexes through one connection.
However, I wonder what the long term goal is here. With all the talk of schemes, temporary .safenet URLs and so forth, what is the vision beyond this? Should the browser be accessing the files directly via FFI, hitting the launcher’s REST API, etc?
I suppose I am asking whether safe:// should actually be HTTP/2 based or whether it should be something completely native. Any thoughts?