On 16 Jan 2012, at 17:09, Daz DeBoer wrote:
G'day
Currently, we are caching changing modules for 24 hours by default.
This means that even though we know the module may change, we only
check for updated version once per day.
I think this confuses users, who expect changing modules (SNAPSHOTs)
to be up-to-date. I'm guessing that maven works this way?
Maven by default has a ttl of 24 hours.
I propose we make 0 seconds the default cache timeout for changing
modules (user configurable).
When we do a check, we follow this process for the meta-data file as
well as any artifacts:1) Attempt to download an SHA1 key for the
artifact2) If the downloaded key matches the current snapshot
artifact, do nothing
3) If there is no SHA1 key, or it does not match, download the
module/artifact
This means that the process is pretty efficient when SHA1 keys are
published.But when no SHA1 keys are published, this would mean that
we'd be downloading the artifacts every time*. (Users could then do
cacheChangingModulesFor 24, 'hours')
Thoughts?
I'm not for this. I think 24 hours is a reasonable default. Even though
the amount of traffic is low for checksum checking, it could still be
painful over a slow/flaky connection.
--
Luke Daley
Principal Engineer, Gradleware
http://gradleware.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
