|I think the notion of which server/repo is best is more in the eye of the beholder than of the producer. p2's artifact download manager should do a decent job of picking the fastest repo/mirror available. It may periodically try a slower one but in the long run fast ones should end up being used. If that is not happening then perhaps it needs to be fixed. I'm somewhat reluctant to say that repo producers should be making assumptions about the consumer's network connections.|
On 2011-02-19, at 2:01 AM, David M Williams wrote:
In particular, is it part of the "spec"
or API? (That is, I'm not just asking about current implementation).
I think this issue will become more
relevant, especially for eclipse.org, now that p2 is getting "old"
:) because some repos that were on 'downloads' should at some point
move to 'archives'.
Let me elaborate. In a composite repo,
many of us might have child repos that might be similar to the following
fictional URLs ...
Is that order, above, treated differently than the
order, below? Which repo is searched (or matched) first for artifacts?
This can become important, for example,
if some artifact is the same in all three repositories .... that is, the
version/qualifier is unchanged. If the "archive" repos are tried
first, then the result would not be mirrored, and always come from eclipse.org
directly, it seems. The opposite would be desired, that 'downloads' repos
would be "searched/matched" first, and if found there, then,
via the magic of the mirrors URL, would have a chance of coming from a
mirror, thus being faster for many users (and off-loading some bandwidth
So, is there a way to make sure 'download'
URLs are matched first? Should they come first in list, or last ... or
is the outcome indeterminable?
Feel free to comment in bug 330134 ...
which was opened some time ago to "investigate" this issue ...
but, I'm hoping some p2 expert knows the answer, and I won't have to investigate
p2-dev mailing list