Eclipse Community Forums: Oomph » stale cache until restart

Help

Home

Home » Eclipse Projects » Oomph » stale cache until restart

Show: Today's Messages :: Show Polls :: Message Navigator

stale cache until restart [message #1820746]

Tue, 28 January 2020 10:12

Julian Honnen

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?

Report message to a moderator

Re: stale cache until restart [message #1821063 is a reply to message #1820746]

Wed, 05 February 2020 04:33

Ed Merks

Messages: 33141
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: https://www.macromodeling.com/

Report message to a moderator

Previous Topic:	Complete versioning support of target / targlet with OOMPH ?
Next Topic:	Create Secure Storage File During Oomph Setup

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 05:13:50 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter