the interface is not so hard, browser needs to communicate via lines
of text to one process. for that it has stdin/out. process that starts
the browser can arrange those fds internally as is needed. doing that
for multiple processes is what i called demuxing.
it doesn't need to be a 9p file server
Hi,
I went a bit further. Each window/tab should be locked to an origin,
and it should have an origin-private browser profile, and process
isolation.
I already produced a proof of concept using surf for webkit1, but
webkit2 doesn't have the necessary navigation hooks in its API.
https://github.co
* hiro 2017-04-14 17:11
> personally i think tabs are stupid. there should be one url and title
> per process.
this!
it's on my todo for long time now to come up with a clean and simple way
to deal with stateful surf sessions (session being an arbitrary number,
N, of current urls (and possibly hi
On 14.04.2017 23:32, hiro wrote:
>> That should be done in a separate session manager process, IMHO.
>
> yes, that's what i mean. it just needs to demux the info from multiple
> browser processes and then just write them to the file exactly like
> opera does right now.
The interesting question is
