Confirmed users
180
edits
Embedding/IPCLiteAPI: Difference between revisions
→Lite-weight Embedding IPC API for Mozilla based applications with native UI.
(→Mer) |
|||
| Line 1: | Line 1: | ||
== Lite-weight Embedding | == Lite-weight Embedding API for Mozilla based applications with native UI. == | ||
<p>Basic architecture is very close to [http://trac.webkit.org/wiki/WebKit2 WebKit2], and [http://browser.garage.maemo.org/docs/browser_paper.html MicroB] | <p>Basic architecture is very close to [http://trac.webkit.org/wiki/WebKit2 WebKit2], and [http://browser.garage.maemo.org/docs/browser_paper.html MicroB] | ||
</p><p>Benefits of new architecture comparing to default [https://wiki.mozilla.org/Embedding/NewApi mozilla embedding]:</p> | </p><p>Benefits of new architecture comparing to default [https://wiki.mozilla.org/Embedding/NewApi mozilla embedding]:</p> | ||
<pre class="_fck_mw_lspace">* No XUL/XPCOM heavy content in UI process (Best memory footprint, fast startup) | <pre class="_fck_mw_lspace">* No XUL/XPCOM heavy content in UI process/Thread (Best memory footprint (process case), fast startup) | ||
* | * Process/Thread communication between UI and Content(Gecko/XPCOM) Thread/Process - built on current Mozilla Chromium/IPDL implementation ([https://developer.mozilla.org/en-US/docs/IPDL/Tutorial IPDL Tutorial]) | ||
* Rendering based on Shadow/Shadowable layers tree (same as content rendering in XUL Mobile FF) | * Rendering based on Shadow/Shadowable layers tree which provide MultiThread/Process responsive rendering (same as content rendering in XUL Mobile FF/OMTC Android Firefox/Firefox OS) | ||
* | * Multi process model provide ability to load memory greedy content in child process and kill it without increasing memory usage for Main UI application process | ||
</pre> | </pre> | ||