The relationship of Java and the client have gone through a number of different incarnations. In the beginning, a Java solution was an applet running via a browser in either a Client/Server or 3-Tier configuration. This was troublesome because each browser had their own implementation of the Java Virtual Machine. This led to overhead as well as the plethora of compatibility issues.

The next step was the innovation of JEE and Java Servlets. This removed the JVM from the embedded client and moved it to the server side. The client didn’t even need Java installed on their machine. All the client required was a browser. The Java backend would deliver the content as HTML to the browser.

This created its own set of problems. Since the client was HTML with a browser, the HTTP protocol meant that you couldn’t definitely maintain state between the client and the server. In addition, a number of features that are available to a Client/Server application such as drag & drop were not available. This was mitigated via Javascript and other elements of the Web 2.0 paradigm. Javascript re-introduced browser version issues. Each browser type and version had a slightly different Javascript implementation. The testing and implementation costs of these solutions caused many project budgets to explode.

This is where webstart provides a solution. It has all of the capabilities of a regular Java client application. It can be save on the desktop  as a shortcut just like any other installed application. The user was not responsible for keeping the application up to date, because the application checks for updates with a remote server each time the application starts. If updates are available, they are installed automatically from the server onto the client.

Click on the link below if you would like to know more on how Sobetech can provide you a Java Webstart Solution

Engage Sobetech for Java Webstart