Not true, Arch could set up a round robin proxy to other mirrors such that when a package is requested it returns a HTTP 302 or HTTP 303 redirect. Then the only network traffic routed through Arch servers would only be the request HTTP headers which is quite insubstantial but would still allow real package statistics to be retrieved.
Kaiting. On Tue, Oct 26, 2010 at 10:55 AM, PyroPeter <abi1...@googlemail.com> wrote: > On 10/26/2010 05:40 AM, Kaiting Chen wrote: > >> Unrelated but thinking ahead, would it be possible to go ahead and get rid >> of /etc/pacman.d/mirrorlist and pull from a main >> http://www.archlinux.org/repository? Then have that repository instead >> be a proxy to the actual >> mirrors that round robin's them, possibly with some kind of IP geolocated >> weighting? Then the package downloads can be easily tracked through this >> main proxy. >> > > To actually track the tcp-traffic (indirectly containing the name of > the requested package) archlinux.org would have to _proxy_ the traffic > (_all_ data would go _twice_ through their network infrastructure). > This would make the concept of mirrors useless. > > The other possibility would be a round-robin domain name > (like e.g. irc.freenode.net). This way archlinux.org could only > log that a connection was made, but not which packages were requested. > (Additionally all mirrors would have to use the same folder hierarchy) > > TL,DR: There is no technical way to monitor all package downloads. > > > Regards, PyroPeter > -- > freenode/pyropeter "12:50 - Ich drücke Return." > -- Kiwis and Limes: http://kaitocracy.blogspot.com/
