Re: PEAR a way forward

Hi Mika, The PEAR Installer already supports mirrors. Again, rsync is not possible with the current model used by pearweb (http://pear.php.net/get as a file Force-Type php), which is why Martin's download.pear.php.net is so important. That site will make mirrors tehcnically possible. Still, it is important to note that the largest load is NOT package downloads, it is 1) xml-rpc 2) pear.php.net/bugs 3) package search These items cannot be successfully mirrored without some kind of master-slave database replication with complex write vs. read mapping to different servers. Yuck. Xml-rpc is not mirrorable because it is only used by outdated security hole-laden PEAR 1.3.x. So, again it comes down to really diving in and knowing what issues are really causing the problems. The biggest bottlenecks are the hardware and the pearweb code itself. Greg -----Original Message----- From: Mika Tuupola <tuupola@appelsiini.net> Subj: Re: [PEAR-DEV] PEAR a way forward Date: Thu Oct 5, 2006 6:52 am Size: 635 bytes To: Greg Beaver <cellog@php.net> cc: Craig Constantine <cconstantine@php.net>,PEAR Dev List <pear-dev@lists.php.net> On Oct 5, 2006, at 7:34, Greg Beaver wrote: > 1) better hardware for pear.php.net > 2) easier development of the code running pear.php.net > 3) better collaboration tools at pear.php.net Even though new hardware will definitely solve many problems some kind of mirroring scheme should be involved. First step could be just mirroring the installable tarballs or packages. This is easy to do with tools like rsync. PEAR installer should then be added a feature to optionally download packages from closest mirror. Fink uses similar feature. http://fink.sourceforge.net/ -- Mika Tuupola http://www.appelsiini.net/~tuupola/