[Onosa]

Hello,

Currently, the users for my application manually download the application using the BlackBerry broswer. The problem is, when a new version of the program is ready, the BlackBerry browser will see the old .jad file instead of the new one that's out there. I'm assuming this is a cache problem, because if a user refreashes the page, they will see the new version with all of it's data (New version number and file size).

Since most users wouldn't think to refresh the page, I need a feature that will always show the current .jad file, which means skipping whatever is in the BlackBerry broswers cache.

Is there a way to do this?

Thank you.

[hrbuckley]

Check the documentation of your Web Server software to see what kind of cache control it provides for files. HTTP caching is controlled by a header sent along with the page (or file) that tells caching proxies and requesting clients how long the file is valid. Browsers will not re-request a file that the server has indicated is still valid unless the user refreshes the page. You may be able to turn caching in the Blackberry off, or reduce it, but you users are not likely to be happy with the results.

[myraddin]

I unfortunately had similar OTA deployment problems with the browser.
It seems that the browser doesn't check (send HEAD request to the http server) the file on the server, but instead just retrieves what it has in the cache.

My problem was solved by manually clearing the cache before every update of the same application.

I am sorry for not having any other idea, just wanted to share the experience I had.

[Onosa]

My users probably wouldn't like to remove the cache before every update. I tried setting the the http header information to no cache, and that seems to work. Thank you for everyones help.

[myraddin]

Originally Posted by Onosa

My users probably wouldn't like to remove the cache before every update. I tried setting the the http header information to no cache, and that seems to work. Thank you for everyones help.

Good trick.
So the Browser obeys that rule ...