Abstract: Embodiments of the present invention relate to a scriptable plug-in API. According to the invention, all of the interfaces in a conventional, non-scriptable plug-in API are mapped to similar interfaces in a scriptable plug-in API. There is no need to change the existing plug-in APIs. In one embodiment, a set of interfaces and a set of wrappers are used to bind the new, scriptable plug-in API to the old one. In another embodiment, C++ wrappers are written to bridge new API to the old one. Inter-threading calls for plug-ins are also made possible using a proxy that functions with scriptable interfaces. In another embodiment, the plug-in is written for a Mozilla™/Netscape™ 6.x browser. In another embodiment, the scripting languages used to develop the plug-in include Python, JavaScript, and Perl.

Abstract: Embodiments of the present invention relate to the implementation of an Application Programming Interface (API) that enables platform independent plug-ins to work with browser applications. In one or more embodiments of the present invention, the API allows platform independent plug-ins to use XPCOM (Cross Platform Component Object Model), a technology that allows software components of different various programming languages to communicate. In one or more embodiments of the present invention, the API enables platform independent plug-ins to take advantage of existing BlackConnect and Scriptable Plug-In API technologies to integrate with the native plug-in API. Embodiments of the present invention ensures backward code compatibility by allowing the current platform independent plug-in API and browser API to remain unchanged. Furthermore, embodiments of the present invention enables platform independent plug-ins to communicate and use components created in native programming languages such as C++.

Abstract: Embodiments of the present invention are directed towards a method and apparatus for calling virtual machine across processes. In one embodiment, it is determined whether a virtual machine is running in the same process. If a virtual machine is running in the same process, that virtual machine is used. If a virtual machine is running in another process, the application sends commands for the virtual machine to an intermediary application in the same process. The intermediary application passes the commands on to another intermediary application in the process where the virtual machine is running, and that intermediary application sends the commands to the virtual machine. Communication from the virtual machine to the application are performed in the reverse order.

Abstract: Embodiments of the present invention relate to a scriptable plug-in API. According to the invention, all of the interfaces in a conventional, non-scriptable plug-in API are mapped to similar interfaces in a scriptable plug-in API. There is no need to change the existing plug-in APIs. In one embodiment, a set of interfaces and a set of wrappers are used to bind the new, scriptable plug-in API to the old one. In another embodiment, C++ wrappers are written to bridge new API to the old one. Inter-threading calls for plug-ins are also made possible using a proxy that functions with scriptable interfaces. In another embodiment, the plug-in is written for a Mozilla™/Netscape™ 6.x browser. In another embodiment, the scripting languages used to develop the plug-in include Python, JavaScript, and Perl.

Abstract: Embodiments of the present invention relate to the implementation of an Application Programming Interface (API) that enables platform independent plug-ins to work with browser applications. In one or more embodiments of the present invention, the API allows platform independent plug-ins to use XPCOM (Cross Platform Component Object Model), a technology that allows software components of different various programming languages to communicate. In one or more embodiments of the present invention, the API enables platform independent plug-ins to take advantage of existing BlackConnect and Scriptable Plug-In API technologies to integrate with the native plug-in API. Embodiments of the present invention ensures backward code compatibility by allowing the current platform independent plug-in API and browser API to remain unchanged. Furthermore, embodiments of the present invention enables platform independent plug-ins to communicate and use components created in native programming languages such as C++.

Abstract: Embodiments of the present invention relate to an implementation of a platform independent plug-in to enable the execution of applications, for example applets, in a host application. In one or more embodiments of the present invention, a plug-in comprises a plug-in API (Application Programming Interface). A host application, for example a web browser, interacts with the plug-in through this interface. An executable launcher is integrated into the plug-in using this interface. In one or more embodiments of the present invention, the executable launcher plays Java applets and JavaBean Components. In one or more embodiments of the present invention, the plug-in is implemented in the Java language. In one or more embodiments of the present invention, the executable launcher is implemented in the Java language.

Abstract: Embodiments of the present invention are directed towards a method and apparatus for remote inter-language method calling. In one embodiment of the present invention, remote inter-language method calls are translated into an intermediary protocol, termed “*Connect”. The call is then translated from *Connect to the protocol of the language in which the method is written. *Connect insures that the method is called properly and that any return values are returned properly. Thus, any change in the protocol of the language in which the method is written necessitates only modification of the code used to translate between *Connect and the method's language.