> B) Now imagine a transparent mirroring solution where step 1 immediately > redirects us to a suitable mirror, and P2 cooperates: > > 1. Request http://download.eclipse.org/foo/updates/latest/p2.index > a. Receive HTTP 307 to http://mirror.example.org/foo/updates/latest/p2.index > b. Update P2 repo object so further repository loading uses the redirected URL > c. Follow redirect and get > http://mirror.example.org/foo/updates/latest/p2.index > 2. Get http://mirror.example.org/foo/updates/latest/compositeContent.jar > 3. Read child URL "../../drops/1.2.3", resolve it to > http://mirror.example.org/foo/drops/1.2.3 >
Hi Carsten, That would certainly make things more efficient from our side: given a p2 repo, provide a mirror location for all the artifacts. Not sure what needs to happen in p2 for that to work, however. Denis _______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
