[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] P2 artifact repositories and caching

There is nothing under development that is not in current project set.  There isn't really any notion of a global artifact cache in p2 - rather artifacts get mirrored from one repository to another as part of an install (typically from a remote repository to a local one). Thus local repositories such as the bundle pool (AggregatedBundleRepository) act somewhat like caches, but there is no notion of cache staleness. If you have artifact with id "foo" and version "1.0.0.v20080318-0800", it is assumed that there is only one unique set of bits associated with it, and once you have those bits there is no possibility of them becoming stale. There is MD5 support today but it is not currently enabled (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=222870).


Thomas Hallgren <thomas@xxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

03/17/2008 06:45 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
[equinox-dev] P2 artifact repositories and caching

In Buckminster, we need a global artifact cache for downloaded things.
What I envision is a cache that can use different strategies to decide
whether or not the local content is up-to-date. One such strategy could
be to compare with a remote digest of some sort (md5 for instance).
Another could be to verify the consistency of a local compressed archive
and be satisfied with the exact same size (not 100% safe of course, but
in some cases its sufficient).

I found the BlobStore in p2 and that will help some. I was under the
impression that a "download manager" was under development that would
address caching issues like the ones I mention. Are there more things
under development that are not covered by the current team project set?

Thomas Hallgren

equinox-dev mailing list