15 ms·

Electrolysis isn't a Servo thing but a Firefox thing. Something that many of us have been waiting for also. From what I've seen with the way Servo works, it s

Electrolysis isn't a Servo thing but a Firefox thing. Something that many of us have been waiting for also. From what I've seen with the way Servo works, it should be working in basically the same way from the beginning but I'm not as confident on that as I'd like to be. Since it renders and works on each iframe in another thread and each tab is implemented as an iframe with mozbrowser extensions I would think it should fix that problem.

Manishearth 12y ago
I think he was talking about Firefox. FWIW in Servo when talking of multiprocess stuff we colloquially call it "Electrolysis". I think Patrick has some work in progress on this. It's not as much work as the Firefox e10s (we already use threads and channels for everything), but I think there is some (relatively) minor work to be done.
- zobzu 12y ago
  how do you handle component sandboxing in Servo compared to firefox e10s? (firefox being child process sandbox, ipc to parent, and things being a little "unperfect" in the separation)
  - pcwalton 12y ago
    The plan is to use gaol [1] for sandboxing. For IPC, we want to send Rust objects serialized via serde [2] over native OS IPC pipes (AF_UNIX sockets on Unix). [1]: https://github.com/pcwalton/gaol https://github.com/pcwalton/gaol [2]: https://github.com/serde-rs/serde https://github.com/serde-rs/serde
    - zobzu 12y ago
      that looks nice i hope the separation between processes themselves will be nicer than firefox (or even chrome) since its "from scratch" :) (ie that it wont be remoting everything and only protect the system from escaping a child - makes sense in firefox/chrome, less with rust being the compiler i guess) I suspect that if servo doesnt try to be an OS like firefox/chrome do, a whole process sandbox may even be fine enough. But if it does.. :)

15 ms·

Electrolysis isn't a Servo thing but a Firefox thing. Something that many of us have been waiting for also. From what I've seen with the way Servo works, it s

by simcop2387 12y ago

Manishearth 12y ago
I think he was talking about Firefox. FWIW in Servo when talking of multiprocess stuff we colloquially call it "Electrolysis". I think Patrick has some work in progress on this. It's not as much work as the Firefox e10s (we already use threads and channels for everything), but I think there is some (relatively) minor work to be done.
- zobzu 12y ago
  how do you handle component sandboxing in Servo compared to firefox e10s? (firefox being child process sandbox, ipc to parent, and things being a little "unperfect" in the separation)
  - pcwalton 12y ago
    The plan is to use gaol [1] for sandboxing. For IPC, we want to send Rust objects serialized via serde [2] over native OS IPC pipes (AF_UNIX sockets on Unix). [1]: https://github.com/pcwalton/gaol https://github.com/pcwalton/gaol [2]: https://github.com/serde-rs/serde https://github.com/serde-rs/serde
    - zobzu 12y ago
      that looks nice i hope the separation between processes themselves will be nicer than firefox (or even chrome) since its "from scratch" :) (ie that it wont be remoting everything and only protect the system from escaping a child - makes sense in firefox/chrome, less with rust being the compiler i guess) I suspect that if servo doesnt try to be an OS like firefox/chrome do, a whole process sandbox may even be fine enough. But if it does.. :)