Markus,
I was reading the JNLP specs
(http://java.sun.com/products/javawebstart/download-spec.html) and in
section 6.3.1 it talks about making incremental updates using JARDiff files.
I think this is a 2 end challenge: the server must be able to provide that
file and the client must be able to understand this type of file.
Since I am new to this JWS technology I have questions regarding both ends.
First of all, how do I set up my web server (Apache) to be able to generate
those JARDiff. I realize that this is not the best place to post this
question but I just thought you may know how to get me started in the right
direction. The second question is if OpenJNLP will be able to use them?
Thanks
Joan
-----Original Message-----
From: Markus Kramer [mailto:Mar...@mp...]
Sent: Wednesday, April 10, 2002 12:58 AM
To: Joan Puig Giner
Cc: ope...@li...
Subject: Re: [Openjnlp-devel] OpenJNLP features
Joan,
JWS and OpenJNLP both run on the client and feed the Java Virtual Machine.
On the server, you need to set up JNLP-descriptions, which point to any
number
of jar files.
If you put newer versions of the jars on your web-server, they will be
looked up
and downloaded.
This behaviour is specified in the JNLP-protocol.
From reading your mail, I get the impression that with "individual file" you
mean a single .class file.
You cannot send single .class files to the client, you have to put them in a
jar.
At my institute, we also develop some rather big applications, and we found
updating/versioning very easy to to with JNLP.
We currently put all bytecode into a single jar file (for each app).
This leads to an update, which will download a lot of unchanged code, but
its
the easiest to organize.
I guess this is what your question is about.
When we want to cut our application into smaller pieces/components, I cannot
see
where DeployDirector is of help.
The ability to specify the download-directory seems to involve more than the
JNLP-protocol allowas, so the DeployDirector must do something extra.
To be onest, I cannot see the benefit of DeployDirector. After going through
the
'Walktrough' of DeployDirector, I get the impression that it is a Graphical
interface to the JNLP-descriptions you can write in any editor (they are
XML).
Please correct me if I understood you wrong.
-Markus
Joan Puig Giner wrote:
> We are planning to develop an application that is going to be rather big
and
> it will be evolving quick. We have been looking at deployment products and
> we have found JWS that makes you download the entire .JAR file and
> DeployDirector that does everything we need but we can't afford it.
>
> (assuming it will be able to tell if a file is up to date or not) my
> question is, does OpenJNLP support individual file download ? if not, any
> plans to implement that within 6 months?
>
> Thanks
> Joan
>
> _______________________________________________
> Openjnlp-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openjnlp-devel
|
