nsISupports proxies

  • Revision slug: nsISupports_proxies
  • Revision title: nsISupports proxies
  • Revision id: 58611
  • Created:
  • Creator: Benjamin Smedberg
  • Is current revision? No
  • Comment XPCOM proxies, removed for sanity.; 71 words added, 1231 words removed

Revision Content

XPCOM proxies were a technology which allowed code to make asynchronous or synchronous XPCOM calls to a different thread on arbitrary XPCOM interfaces. This technology has been removed in Firefox 12 because it was very complex and often lead to strange deadlock conditions. It is no longer needed because JavaScript code can no longer run on arbitrary threads, and compiled code can use compiled runnable to achieve the same effect in a much simpler manner. For more information about alternatives, see Making Cross-Thread Calls Using Runnables.

The following interface was now obsolete: nsIProxyObjectManager.

Revision Source

<p class="note">XPCOM proxies were a technology which allowed code to make asynchronous or synchronous XPCOM calls to a different thread on arbitrary XPCOM interfaces. This technology has been removed in Firefox 12 because it was very complex and often lead to strange deadlock conditions. It is no longer needed because JavaScript code can no longer run on arbitrary threads, and compiled code can use compiled runnable to achieve the same effect in a much simpler manner. For more information about alternatives, see <a href="/en/Making_Cross-Thread_Calls_Using_Runnables" title="en/Making Cross-Thread Calls Using Runnables">Making Cross-Thread Calls Using Runnables</a>.</p>
<p class="note">The following interface was now obsolete: nsIProxyObjectManager.</p>
Revert to this revision