Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » stale cache until restart
stale cache until restart [message #1820746] Tue, 28 January 2020 10:12 Go to next message
Julian Honnen is currently offline Julian HonnenFriend
Messages: 2
Registered: January 2020
Junior Member
Oomph seems to prefer the locally cached setup file instead of reading an update from the server. Our setup model is accessed via http and the server returns ETags.

An updated setup model is only loaded from server after an eclipse restart (or when manually using "Refresh Remote Cache").

I looked at the logic in ECFURIHandlerImpl.ConnectionHandler.process(), but I don't quite understand it. The etag of the locally cached file is compared to a cached expected etag (EXPECTED_ETAGS).
But that check should always succeed (as long the the cache file is not touched), right? Why is there no conditional request sent?

Is there an option to disable caching?
Re: stale cache until restart [message #1821063 is a reply to message #1820746] Wed, 05 February 2020 04:33 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 32111
Registered: July 2009
Senior Member
Yes, once the ETag has been checked, the locally cached version will always be used until ECFURIHandlerImpl.clearExpectedETags() is called. There is no option to disable this.

In general, hundreds of resources will be loaded when loading the Index. Waiting for server responses on all of them each time would lead to long(er) delays in a many places, e.g., opening an editor.

Ed Merks
Professional Support:
Previous Topic:Complete versioning support of target / targlet with OOMPH ?
Next Topic:Create Secure Storage File During Oomph Setup
Goto Forum:

Current Time: Sun Dec 05 05:58:56 GMT 2021

Powered by FUDForum. Page generated in 0.01698 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top