Okay, thats something i have to think about. In this case the applet
is yust a way of using an application without the need to download it,
so Webstart seems just to do that.
Thank you for that hint.
Peter
On Mar 17, 10:37 pm, pkoer...@online.de wrote:
> Hi there
>
[quoted text clipped - 4 lines]
> is yust a way of using an application without the need to download it,
> so Webstart seems just to do that.
Actually, it is more complicated, subtle, and
useful than perhaps I described it.
In seems to the end user, that no 'installation'
happened, where in effect, it does. The classes
and resources are cached locally. When the user
launches the application (or applet) again, web
start checks the net to see if there are any
updates, but if it cannot, or there aren't any,
it will launch the app. from the cache.
Further, resources can be specified as either
'eager' or 'lazy'. Lazy means that the resource
is not download until, or unless, the user needs
that funtionality (think of an entire API that
provides printing support to an app. - if the
user never wants to print, why download it?)
Andrew T.
pkoerner@online.de - 18 Mar 2007 18:27 GMT
I found this one [http://www.physci.org/jws/#fs] as an example what
can be done with JWS and it is very cool to see that JWS only asks for
file-save-permissions, when really a file should be saved. I think
that's what i want to have my own application acting like, so i will
change the applet-functionality into an webstart-service.
Thank you for your hints,
Peter
Andrew Thompson - 19 Mar 2007 02:54 GMT
On Mar 19, 4:27 am, pkoer...@online.de wrote:
> I found this one [http://www.physci.org/jws/#fs] as an example what
> can be done with JWS and it is very cool to see that JWS only asks for
> file-save-permissions, when really a file should be saved.
Yes, I like that aspect of it, as well.
>..I think
> that's what i want to have my own application acting like, so i will
> change the applet-functionality into an webstart-service.
> Thank you for your hints,
You're welcome.
Andrew T.