Prevent caching of JARs
Dear Friends,
somtime I actualize my JAR-Files.
And I don't want that the user has to delete his java-Cache, etc. - That's not acceptable for that group of users.
How can I prevent caching of my JAR-File?
The JAR is only 70 kb big and wouldn't disturb.
Well, actually I use a meta pragma nocache - but does that really help?
Is there a secure way to prevent the caching to the harddrive (after a browser-session) ?
Thank you!
With best regards
MfG
Inno
> Dear Friends,
>
> somtime I actualize my JAR-Files.
What is that trying to say ?
Does your jar have feelings and dreams - is it trying to better itself ? (Sorry I couldn't help, just did a psych test ;-P )
In all seriousness it would help if you explain what type of program this is, what you mean by caching jars, and why it is an issue.
> And I don't want that the user has to delete his
> java-Cache, etc. - That's not acceptable for that
> group of users.
>
> How can I prevent caching of my JAR-File?
> The JAR is only 70 kb big and wouldn't disturb.
>
> Well, actually I use a meta pragma nocache - but does
> that really help?
>
> Is there a secure way to prevent the caching to the
> harddrive (after a browser-session) ?
>
> Thank you!
> With best regards
> MfG
> Inno
I use an applet on a html-page.
And here is the problem:
When I upload a new JAR to the server the client still uses the cached jar which he has downloaded some day (months, years?) before.
And I want to prevent it.
So we have:
a) A html-Page
b) An applet on this page
c) A .JAR-File contains the classes of the applet.
And I want that the client doesn't cache the jar.
The client should _always_ download it freshly from the server!
Otherwise my JAR is so lonely and sad :-)
With best regards
MfG
Inno
> Otherwise my JAR is so lonely and sad :-)If your jar file is self-actualised, then at least it will know why it is lonely and sad.
if the purpose of this is to test your applet, try using the appletviewer application that comes with the JRE. I remember having similar problems many years ago with cached applets, and appletviewer was my solution during development.
> if the purpose of this is to test your applet, try
> using the appletviewer application that comes with
> the JRE. I remember having similar problems many
> years ago with cached applets, and appletviewer was
> my solution during development.
I am pretty sure that he mentioned this as a user request above.
If your JAR file is a different version than the one in the client plug-in cache then it should automatically download the new version.
My question is, if the client has your JAR file in their cache for 2 years but they are still downloading the same version then why should they redownload a file that they already have in their cache?
> > if the purpose of this is to test your applet, try
> > using the appletviewer application that comes with
> > the JRE. I remember having similar problems many
> > years ago with cached applets, and appletviewer
> was
> > my solution during development.
>
> I am pretty sure that he mentioned this as a user
> request above.
>
> If your JAR file is a different version than the one
> in the client plug-in cache then it should
> automatically download the new version.
Do I need to define the version somewhere in my JAR?
With best regards
MfG
Inno
