[Openjnlp-devel] Furher development of OpenJNLP
Brought to you by:
kherr
From: <Jan...@tk...> - 2003-04-15 07:36:44
|
Hi ! We're using OpenJNLP for updating our enterprise-software-clients. We choosed OpenJNLP over WebStart because we can't pass command-line arguments to WebStart, and we don't want sandbox-security. Now in out production environment, we've got some problems, which I hope to have fixed: 1. When a download is interrupted due to a network error, the downloaded file was left currupted. 2. Version-based downloading was not implemented, but obviously prepared. 3. The JNLP-Spec doesn't address, how to deal with version-information if the URL is a file://-URL. The implementation of Sun's FileURLConnection just ignores parameters on file-URLs (file://localhost/Q:/foo/bar?version-id=2.3 becomes Q:\foo\bar on Win32). The solutions we chose were: 1. Downloading into a temporary file, copy to the cache after successful download. 2. We implemented it ;-). But this required some massive code-changes, mostly in CachedResouce.java. How should we deal with this, I'm frightened of having to integrate out changes into the next OpenJNLP-Release. Another issue is I used the jardiff.jar for patching the JarDiffs delivered by the JNLPDownloadServlet. Are there any legal issues? 3. If version-information is provided with a file URL, the naming-convention of the JNLPDownloadServlet is used so the file for the above URL would be: Q:\foo\bar__V2.3 CU Jan Koops (Hamburg, Germany) |