Changing the current mirror behavior might be
confusing to users so I think it's better to retire the old mirror
functionality and provide the new one with a new name.
>>Why? If the content servers are overloaded, the origin might still be
capable of serving the data, and might be faster.
Yes, but like mentioned above, I think the origin should not be
considered for the auto-tune. It might not even be an issue because the
http downloads over akamai are probably always faster than the https
downloads from pkg.oracle.com but we should try to transport files over
the alternate source if possible.
* If clients are routinely connecting to multiple servers to obtain
content, that might defeat any local proxy-caching that's going on
(since the proxy could have references to multiple URLs containing the
same content) For example, this could upset the system repository cache
on systems with lots of zones.
Will it actually upset the cache? I could imagine you just end up with
the same file/content under different hashes. So it would require
additional space but still be correct, not?
[pkg-discuss] Re: The future of the pkg mirror