How does Aplix’s NPAPI Java plugin differ to that of Sun’s?

The last incarnation of Java plugin support from a browser was LiveConnect. So let’s compare WebVM to LiveConnect.

Use the Web platform, not the Java platform

LiveConnect lets Web developers call arbitrary methods on the J2SE VM. This disruptive technology encourages developers to use the non-Web language Java. WebVM encourages Web developer to simply use familiar JavaScript interfaces instead.

WebVM in practice limits Web Developers access to Java implementations of device APIs missing on the browser platform, encouraging Web developers to concentrate on building an innovative Web application, not a Java application.

Mobile focused

Though Apple for example claim to support LiveConnect in their upcoming Safari 3, there is couple of issues with this. Firstly implementation isn’t there.

The most interesting platform for WebKit is the mobile space. Apple offerings such as the Ipod Touch/Iphone do not have a Java VM and are unlikely to do so.

Aplix has a wealth of expertise with millions of JBlend deployments on mobile devices. WebVM deployed with JBlend will have a much bigger impact in the technology space that matters.

Faster

LiveConnect’s reflection J2SE API is very heavy. WebVM has a custom stub compiler to speed up the mapping of Javascript to Java objects. WebVM should be faster than LiveConnect, which it must be on limited mobile devices.

WebVM limits calling methods on a single DOM node. This is much more efficient and self-contained, compared to LiveConnect.

Future compatible

JavaScript is flexible enough to wrap and abstract any interface exposed by Java to meet any future device API standard.