Comments on: I’ve seen the future, brother: it is dynamic additions to the status bar that don’t block the main process. http://www.joshmatthews.net/blog/2010/03/ive-seen-the-future-brother-it-is-dynamic-additions-to-the-status-bar-that-dont-block-the-main-process/ /* You are not expected to understand this */ Sat, 04 Feb 2012 03:50:26 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Josh Matthews http://www.joshmatthews.net/blog/2010/03/ive-seen-the-future-brother-it-is-dynamic-additions-to-the-status-bar-that-dont-block-the-main-process/comment-page-1/#comment-333 Josh Matthews Wed, 17 Mar 2010 08:37:37 +0000 http://www.joshmatthews.net/blog/?p=69#comment-333 Wladimir: this is using the <a href="https://wiki.mozilla.org/Electrolysis" rel="nofollow">Electrolysis</a> work as a base. The "signaling overhead" you refer to is exceedingly low; the IPDL technology we're using is quite responsive and easy to work with. The eventual goal is to have a separate process for Jetpacks (maybe per Jetpack, I'm unclear on that point right now); I recommend seeing <a href="https://developer.mozilla.org/en/Multi-Process_Architecture/Jetpack" rel="nofollow">the wiki</a> for a general overview of future plans. The process of moving them out of process is unavoidable - seeing as Firefox is going to be split into chrome/content processes and Jetpacks by necessity span both, I'm doing the investigation now to figure out how best to go about it. Wladimir: this is using the Electrolysis work as a base. The “signaling overhead” you refer to is exceedingly low; the IPDL technology we’re using is quite responsive and easy to work with. The eventual goal is to have a separate process for Jetpacks (maybe per Jetpack, I’m unclear on that point right now); I recommend seeing the wiki for a general overview of future plans. The process of moving them out of process is unavoidable – seeing as Firefox is going to be split into chrome/content processes and Jetpacks by necessity span both, I’m doing the investigation now to figure out how best to go about it.

]]> By: Wladimir Palant http://www.joshmatthews.net/blog/2010/03/ive-seen-the-future-brother-it-is-dynamic-additions-to-the-status-bar-that-dont-block-the-main-process/comment-page-1/#comment-331 Wladimir Palant Wed, 17 Mar 2010 08:08:03 +0000 http://www.joshmatthews.net/blog/?p=69#comment-331 So, it took you 2.5 months to add "Gmail it" to the status bar that doesn't even work? I can do that in 2.5 minutes! :) But on a more serious note: How does this work, some new IPC API? For simple extensions, won't the signaling overhead be larger that the time this extension would normally spend on the main thread? And is the idea to move all Jetpack extensions out of process or is it going to be an opt-in thing? So, it took you 2.5 months to add “Gmail it” to the status bar that doesn’t even work? I can do that in 2.5 minutes! :)

But on a more serious note: How does this work, some new IPC API? For simple extensions, won’t the signaling overhead be larger that the time this extension would normally spend on the main thread? And is the idea to move all Jetpack extensions out of process or is it going to be an opt-in thing?

]]>