{"json_modified": "2016-03-28T08:14:12.093894", "uuid": "d7cd9aa9-9c72-4d3a-aefa-7f21abc55228", "title": "Bundling multiple binary components", "url": "/en-US/docs/Mozilla/Tech/XPCOM/Bundling_multiple_binary_components", "tags": [], "translations": [], "modified": "2016-02-29T10:46:42", "label": "Bundling multiple binary components", "localization_tags": [], "locale": "en-US", "id": 16037, "last_edit": "2009-07-17T08:06:26", "summary": "Binary XPCOM components are sometimes required to implement low-level features for extensions. Since binary components are linked against a single Gecko SDK, a dependency to a particular version of Gecko is created. If the component uses only \"frozen\" XPCOM interfaces, there is a good chance the same binary component will work with different versions of Gecko (version 1.8 and 1.9, for example). The more likely case is that the component uses \"unfrozen\" interfaces and those interfaces can change between Gecko versions. This can create a difficult situation for extension developers trying to support multiple Gecko versions (Firefox 2 and 3, for example).", "sections": [{"id": "Background", "title": "Background"}, {"id": "Possible_Solutions", "title": "Possible Solutions"}, {"id": "Dynamic_method_loading", "title": "Dynamic method loading"}, {"id": "Stub_loader", "title": "Stub loader"}], "slug": "Mozilla/Tech/XPCOM/Bundling_multiple_binary_components", "review_tags": []}