
	Where results make sense

Topic: XPConnect

In the News (Wed 23 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	XPConnect - Definition, explanation
		XPConnect (Cross Platform Connect) is a technology which enables simple interoperation between XPCOM and scripting programming language like JavaScript.
		A main goal is that objects communicating from either side of an XPCOM style interface should not generally need to know or care about the implementation language of the object on the other side of the interface.
		XPConnect's primary reason for existence is to replace handwritten code used in places where native code needs to interact with JavaScript code.
	www.calsky.com /lexikon/en/txt/x/xp/xpconnect.php (186 words)

	NationMaster - Encyclopedia: XPConnect (Site not responding. Last check: )
		XPConnect (Cross Platform Connect) is a technology which enables simple interoperation between XPCOM and scripting programming language like JavaScript.
		XPConnect's primary reason for existence is to replace handwritten code used in places where native code needs to interact with JavaScript code.
		XPConnect is a technology which enables simple interoperation between XPCOM and JavaScript.
	www.nationmaster.com /encyclopedia/XPConnect (580 words)

	Scriptable Components (XPConnect)
		XPConnect is a technology which enables simple interoperation between XPCOM and JavaScript.
		The XPIDL compiler is used to generate both C++ header files and XPConnect typelib files.
		The typelib files allow the XPConnect glue code to dynamically build proxy objects at runtime to dispatch method calls and handle property accesses between XPCOM and JavaScript objects.
	www.mozilla.org /scriptable (626 words)

	WebReference.com - Part 3 of chapter 5 from Creating Applications with Mozilla. From O'Reilly (1/4).
		This is where XPConnect and XPCOM come in.
		In Mozilla, XPConnect is the bridge between JavaScript and XPCOM components.
		The XPConnect technology wraps natively compiled components with JavaScript objects.
	www.webreference.com /programming/javascript/mozillaapps/chap5/3 (549 words)

	JavaScript XPCOM Components Status
		The source of this problem was that xpconnect was giving the calling JS code direct access to the underlying JSObject of the JS Component.
		This meant that the caller had access to all of the methods and properties of the JS Component and was not limited by the declared interface.
		This means that when the JS Component is created and handed to native code xpconnect builds a wrapper to be used by the native code AND when that wrapper is later handed to JS code then xpconnect builds a wrapper around that wrapper for use from JS.
	www.mozilla.org /scriptable/js-components-status.html (888 words)

	Symantec Security Response Weblog: BHO and XPCOM: Extensions Gone Wild
		In March 2006 we found the first in-the-wild case with JS.Ffsniff, which is a JavaScript that uses XPConnect.
		XPConnect is an interface for JavaScript that allows transparent access to XPCOM objects.
		The threat is part of a browser extension; once installed, it will add itself as an event listener for all “form submit” events.
	www.symantec.com /enterprise/security_response/weblog/2006/07/bho_and_xpcom_extensions_gone.html (515 words)

	XPConnect and Scriptable Components
		In Mozilla, XPConnect is the bridge between JavaScript and XPCOM components.
		Using JavaScript and XPConnect, you can create instances of these components and use their methods and properties as you do any regular JavaScript object, as described here.
		In Example 5-11, an HTML file (stored locally, since it wouldn't have the required XPConnect access as a remote file because of security boundaries) loaded in Mozilla instantiates a Mozilla sound component and plays a sound with it.
	docs.mandragor.org /files/Misc/Mozilla_applications_en/mozilla-chp-5-sect-4.html (0 words)

	Aggreg8.net: Philip Roche (Site not responding. Last check: )
		XPCOM (Cross Platform Component Object Model) and XPConnect (Cross Platform Connection to Components) are complementary technologies that enable the integration of external libraries with XUL applications.
		Together, XPCOM and XPConnect enable developers to create XUL applications that require the raw processing power of compiled languages (C/C++) or access to the underlying operating system.
		The main feature of XPCOM and XPConnect that was used in Aggreg8 was the ability to manipulate an RDF (Resource Description Framework) file.
	www.philroche.net /redbrick/CA4Project (792 words)

	XPConnect object wrapping - MozillaWiki
		They are manufactured by XPConnect in order to cache the results of a QI performed by script code manipulating a wrapped native.
		Every time a script accesses it as an nsIFoo, XPConnect is obliged to QI the nsISupports to nsIFoo.
		To avoid doing this on every call, XPConnect builds a an XPCWrappedNativeTearOff after the first QI and stores an XPCNativeInterface, a reflected JSObject, and the nsISupports returned from the QI (which may itself be a normal XPCOM tearoff, so is not necessarily the base nsISupports).
	wiki.mozilla.org /XPConnect_object_wrapping (1321 words)

	XPConnect - MDC
		XPConnect is a bridge between JavaScript and XPCOM.
		With XPConnect, you can use XPCOM components from JavaScript code, and interact with JavaScript objects from within XPCOM components.
		What sorts of wrappers XPConnect generates and uses
	developer.mozilla.org /en/docs/XPConnect (52 words)

	JavaScript-DOM Prototypes in Mozilla
		The prototype objet that XPConnect creates for the classes that have classinfo are shared within a scope (window).
		As the prototype property of the constructor function is being defined, the code also sets up the prototype of the prototype property of the constructor function (i.e.
		The beauty of this code is that the prototype property of a class constructor is the real XPConnect prototype for that class.
	www.mozilla-japan.org /docs/dom/mozilla/protodoc.html (1382 words)

	[No title] (Site not responding. Last check: )
		Those libraries are currently co-dependent so they should really be in a single heirarchy from a build standpoint.
		And that pretty much sets the precedent for moving xpconnect, liveconnect, necko & ipc back inside gecko.
		xpconnect could be a top-level module if the dependency in bug 183321 was resolved & jsloader was made a separate module which lived inside gecko.
	www.seawood.org /mozilla/reorg-prototype-postmortem.txt (1177 words)

	Interface Reference - nsIXPConnect
		Set fallback JSContext to use when xpconnect can't find an appropriate context to use to execute JavaScript.
		XPConnect builds internal objects that parallel, and are one-to-one with, the JSContexts in the JSRuntime.
		This method tells XPConnect to resynchronize its representations with the list of JSContexts currently 'alive' in the JSRuntime.
	www.xulplanet.com /references/xpcomref/ifaces/nsIXPConnect.html (779 words)

	Performance:Leak Tools - MozillaWiki
		This can mean there will be XPConnect wrapper objects showing up as owning the leaked objects, but it doesn't mean it's XPConnect's fault (although that has been known to happen, it's rare).
		Debugging leaks that go through XPConnect requires a basic understanding of what XPConnect does.
		XPConnect allows an XPCOM object to be exposed to JavaScript, and it allows certain JavaScript objects to be exposed to C++ code as normal XPCOM objects.
	wiki.mozilla.org /Performance:Leak_Tools (2774 words)

	Mozilla ActiveX Plug-in
		If you want scripting in Mozilla then the use of XPConnect via the NPAPI is the only recommended method and strongly encouraged - it's actually a lot more powerful and tightly coupled to Mozilla (e.g.
		Uses an XPConnect Type library (XPT file) to define the scriptable API to the browser.
		The XPConnect implementation relies on the nsIVariant object supported by Mozilla 1.0 and later.
	www.iol.ie /~locka/mozilla/plugin.htm (2882 words)

	BSBlog » Blog Archive » XPCOM: Detecting Reference Cycles, or Switching to GC?
		In addition, xpconnect wrappers (and hopefully javaxpcom and pyxpcom wrappers) can participate in a unified GC.
		This entry was posted on 18 Feb, 2006 at 10:50 am and is filed under planetmoz.
		In my proposal the ordinary case would be for an object to have a refcount of zero: nsIGCThing-based interfaces are not refcounted.
	benjamin.smedbergs.us /blog/2006-02-18/xpcom-detecting-reference-cycles-or-switching-to-gc (1879 words)

	Is this a bug or something wrong with my pc?? (Site not responding. Last check: )
		When I click on the view photostream icon with a flickr or photobucket image in the bottom left, it comes up with "oops: [xpconnect...
		Bug 4133An error returning from the "View photostream button" displays Error: XPConnect...
		The content of this field is kept private and will not be shown publicly.
	flock.com /forums/is-this-a-bug-or-something-wrong-with-my-pc (153 words)

	Javascript File i/o - MozillaZine Talkback (Site not responding. Last check: )
		There may never be one, because XPConnect is so broad and easily extensible.
		All access to XPConnect is considered as high risk, i.e., UniversalBrowserAccess.
		There is no low risk access to XPConnect or XUL, which is why the term "skins", as used in the mozilla codebase, does not allow for customizable button functionality.
	www.mozillazine.org /talkback.html?article=1425&message=21&state=reply (428 words)

	1999 Linux Symposium: mozilla
		We'll look at how to work with RDF data sources and how to implement your own.
		XPConnect is the technology that allows JavaScript to manipulate and even implement XPCOM interfaces.
		With much application logic written as JavaScript poking at XPCOM components, XPConnect is a critical part of the Mozilla architecture.
	www.linuxsymposium.org /1999/mozilla.php (284 words)

	ASPN : PyXPCOM : PyXPCOM documentation
		Thus, we are able to get by with far fewer interfaces supported in the C++ level, and defer most things to the Python code that uses XPConnect.
		There are, however, a number of interfaces that do require native C++ support: these are interfaces required to "boot" the XPConnect support (i.e., the interfaces that are used to get information about interfaces), and also two gateways that need to work without interface information available.
		This last requirement is due to the XPCOM shutdown-ordering - it may be a bug, but is not an unreasonable amount of code anyway.
	aspn.activestate.com /ASPN/Downloads/Komodo/PyXPCOM/doc/architecture (549 words)

	XPCOM
		Roadmap for XPCOM, XPConnect, XPTCall, and XPIDL describes how they all fit together
		XPConnect describes how XPCOM based classes can be accessed through JavaScript.
		XPIDL is the XP Interface Description Language used to specify XPCOM interface classes
	www.mozilla.org /projects/xpcom (369 words)

	Is XPConnect/XPCOM deprecated for embedded Spidermonkey? - MozillaZine Forums (Site not responding. Last check: )
		First, we discovered that you can write C++ wrapper classes for each of the native C++ classes, in order to expose them in Javascript.
		Now, I understand that npruntime has deprecated XPConnect for plugins to the Mozilla application.
		Your assumption about deprecating XPConnect for plugins is probably correct.
	forums.mozillazine.org /viewtopic.php?t=307374 (277 words)

	Plug-in Development Overview
		Plug-ins that formerly used LiveConnect to make themselves scriptable in 4.x Netscape browsers have lost this possibility in the new XPCOM architecture upon which Netscape Gecko-based browsers are based.
		Where LiveConnect was a bridge between Java and JavaScript, XPCOM is a more general framework for making components scriptable from the browser.
		In order to make plug-ins accessible via XPConnect, however, some changes have been made to the Mozilla code, and there are also some modifications you will have to make to your plug-in code.
	devedge-temp.mozilla.org /library/manuals/2002/plugin/1.0/develop.html (3533 words)

	XPConnect 'Components' Object Reference
		XPConnect 機能は Components オブジェクトを介して JavaScript へ反映されます。実際には、Components オブジェクトは XPConnect を利用するトップレベルのオブジェクトとして、 JavaScript へ反映される nsIXPCComponents インターフェースのネイティブインスタンスです。
		Components.lastResult は直前の xpconnect を介した xpcom メソッド呼び出しのリザルトコードである数値 nsresult code を返します。一般的に、これは 'success' code を返す xpcom メソッドの結果のテストにのみ役立ちます。というのは、失敗したリザルトコードは xpconnect が例外に変換して、呼び出し JS メソッドへ投げるからです。ほとんどのインターフェースは 1つだけの success code ― NS_OK ― だけを返すので、Components.lastResult はほとんど必要ありません。
		Components.returnCode は、JS メソッドの xpcom 呼び出し側へ、メソッドが特別な nsresult コードを返すことを示すのに利用できるプロパティです。一般的には、xpconnect は JavaScript コードが nsresult コードを心配する必要の無いようにうまく働きます。デフォルトでは、JS メソッドが成功裡に終わると xpconnect は 'NS_OK' リザルトコードを返します。もし JS コードが失敗のシグナルを送る必要がある場合は、例外を投げることで果たします。しかし、success code 返り値を規定したごく僅かな xpcom インターフェースが存在します。Components.returnCode はそれら稀なインターフェースを JavaScript で実装できるようにするために存在します。
	www.mozilla-japan.org /scriptable/components_object.html (590 words)

Try your search on: Qwika (all wikis)