Re: java webstart
From: Richard Chrenko (richard.chrenko_at_solarenergy.ch)
Date: 03/26/04
- Next message: Bent C Dalager: "Re: java webstart"
- Previous message: Tom: "Re: IE & applets"
- In reply to: Bent C Dalager: "Re: java webstart"
- Next in thread: Bent C Dalager: "Re: java webstart"
- Reply: Bent C Dalager: "Re: java webstart"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 26 Mar 2004 17:42:10 +0100
On Fri, 26 Mar 2004 11:56:45 +0000 (UTC), Bent C Dalager <bcd@pvv.ntnu.no>
wrote:
> In article <opr5fhc5m1caoj5g@news.hsr.ch>,
> Richard Chrenko <richard.chrenko@solarenergy.ch> wrote:
>>
>> 1. Internet updates can not be disabled. For a simulation program,
>> getting different results after an automatic (invisible) update will
>> give our customers fits. Although there appears to be some JSP-based
>> server-side versioning capability, this was more effort than we wanted
>> to spend.
>
> I believe the user can disable it on a JWS-wide scale by clicking an
> "off-line" checkbox in the JWS config utility.
Thanks for the tip! I just tried this and it appears that the setting is in
fact on a per-application basis. However, there is a 20-30 second delay
before the application starts locally which I presume to be a network
timeout (hopefully editable!).
>
>> 2. Downloads are limited to JAR files. For database updates, we would
>> have to pack our SQL scripts and data into a JAR file and unpack and
>> manually update table data on the client.
>
> Why couldn't you just do online table-lookups directly from the client
> utility when necessary?
Our application uses a client-side embedded database. The first problem in
that the initial installation of the database requires not only copying the
relevant DB engine JAR files but also extracting the data files from the
JAR and setting the connection path. This is easier using an installer.
We will provide product information updates (a few MB) on a regular basis.
These updates could theoretically be done by the application over the
network, but this appears much more complex and error-prone than
downloading files and having the client do the update locally.
>
>> 3. Predefined application home. You cannot prompt the user to install
>> the application where they please. It is instead automatically saved to
>> a uniquely named directory somewhere beneath the Web Start home
>> directory.
>
> Why is it necessary for your users to have this sort of micro-control?
It's not really necessary from the developer perspective, but for customer
support purposes it's easier to tell the user to search for the application
directory which he himself chose. Also, it's not clear to me how Web Start
manages program versions or what happens when the customer upgrades to a
new version of Web Start. With an installer the customer is always in
control of his installation path.
>
> Cheers
> Bent D
- Next message: Bent C Dalager: "Re: java webstart"
- Previous message: Tom: "Re: IE & applets"
- In reply to: Bent C Dalager: "Re: java webstart"
- Next in thread: Bent C Dalager: "Re: java webstart"
- Reply: Bent C Dalager: "Re: java webstart"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
