Launcher
From Vexi
The launcher is the program run by the browser to launch Vexi. Its configuration determines what Vexi code should be executed, i.e. which application should be run. It caches files (versions of the Core, Vexi Archives) in the Vexi Directory. Making sure uninstalled/updated files are downloaded before launching Vexi. In addition it is a link in the Chain of Trust and a full implementation should verify its downloads.
Contents |
Current Implementations
Java Applet
The current implementation is a signed applet. Core verification is unmaintained/incomplete.
Other Possible Implementations
Java Webstart
Aside from code reuse, Java Webstart offers better potential compatibility across existing and future systems as it has access to available installed JVMs. The applet contains system specific code for locating the preferred Java binary.
Native Launchers
In the event that the Native Binaries make a comeback it will be desirable to have native launchers, as using an applet necessitates the installation of Java, avoiding which is half the reason to use Native binaries in the first place (the other reason being optimized performance). As native launchers are inherently not cross platform, a javascript pre-launcher has to exist to determine the host Operating System/Browser. The prototype was code named 'Catapult'.
- ActiveX Control - Windows & IE
- XUL - Mozilla Browsers
