Hi, On Tue, Mar 16, 2010 at 8:59 PM, Tomasz Sterna <[email protected]> wrote: > Dnia 2010-03-16, wto o godzinie 10:36 +0200, Alexander Bokovoy pisze: >> Unfortunately, there is no common support for that in current Gecko >> and WebKit implementations, they only support in-process EAL/UI >> separation. There is ongoing work on Mozilla side to have something >> similar to MicroB out-of-process separation (Electrolysis, >> https://wiki.mozilla.org/Electrolysis). One particular reason why it >> is relatively hard to do is due to use of the same event loop for both >> UI and EAL event processing. > > IIUC in Maemo EAL does not need to create any UI. It only sends/receives > D-BUS events and is perfectly fine with separate event loop - EAL runs > in separate proces under control of browserd and it's event loop handles > only I/O and rendering the page. The whole UI is handled in Browser > process separately. And it took Maemo browser team 1.5 year to develop this solution (it does not use D-BUS for interacting between EAL process and UI process, btw). Just to measure complexity and what you need to do. What you are missing here is that this process separation for engine and UI is not yet finished for upstream Gecko/Firefox (see Electrolysis) and not done for WebKit except for specific instance used within Chrome.
So, yes, re-using Tablet Browser process separation is nice but expecting that things will work with QtWebKit interfacing with it is rather optimistic. -- / Alexander Bokovoy _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
