Embedding/IPCLiteAPI: Difference between revisions
Jump to navigation
Jump to search
(Basic description) |
No edit summary |
||
| Line 1: | Line 1: | ||
<h3> Lite-weight Embedding IPC API for Mozilla based applications with native UI. </h3> | <h3> Lite-weight Embedding IPC API for Mozilla based applications with native UI. </h3> | ||
<p>Basic architecture is very close to | <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 | </p><p>Benefits of new architecture comparing to default [https://wiki.mozilla.org/Embedding/NewApi mozilla embedding]</p> | ||
</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 (Best memory footprint, fast startup) | ||
* IPC use current Mozilla Chromium/IPDL implementation (mostly tested with current FF/Mobile) | * IPC use current Mozilla Chromium/IPDL implementation (mostly tested with current FF/Mobile) | ||
Revision as of 22:05, 30 December 2011
Lite-weight Embedding IPC API for Mozilla based applications with native UI.
Basic architecture is very close to WebKit2, and MicroB
Benefits of new architecture comparing to default mozilla embedding
* No XUL/XPCOM heavy content in UI process (Best memory footprint, fast startup) * IPC use current Mozilla Chromium/IPDL implementation (mostly tested with current FF/Mobile) * Rendering based on Shadow/Shadowable layers tree (same as content rendering in XUL Mobile FF) * IPC provide ability to load memory greedy content in child process and kill it without increasing memory usage for Main UI application process