Re: unofficial mirror warning for cc.php.net
| From: | Hannes Magnusson | Date: | Fri, 01 Feb 2013 17:54:29 +0000 |
| Subject: | Re: unofficial mirror warning for cc.php.net | ||
| References: | 1 2 3 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-39697@lists.php.net to get a copy of this message | ||
On Fri, Feb 1, 2013 at 12:19 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote:
>
>>
>> > I would also like to know what was the original plan for the
>> > introduction of the cc.php.net
>> > <http://cc.php.net> loadbalanced domains?
>> > I suppose we planned to phase out the invidual mirror selection on My
>> > php.net <http://php.net> and redirecting to
>> > invidual mirrors in favor of
>> > using these round robined domains.
>>
>> I don't think we need to phase that out. It can be handy to let users
>> hardcode a specific mirror for latency reasons.
Yep. People should still be able to set their cookie to their favorite mirror.
> Personally I agree with you that it would be the best to keep the separate
> mirror subdomains and the user's ability to select a mirror explicitly.
> But I suppose there were some plan to direct more traffic to the cc.php.net
> domains
> Currently we don't propagate those, and they are only getting traffic (I
> guess) because in the pre-round-robin times the primary mirror was always
> called cc.php.net and there is a bunch of random places on the internet
> which has links for those domains..
> Am I missing something here?
No plans for phasing out ccN.
The reason for the round robin is to always have cc.php.net available,
previously we would have to shuffle the cc2 into cc when the original
mirror got deactivated or removed, which is annoying.
Users shouldn't have to remember "cc2.php.net", they access their
countries mirrors directly via cc.php.net and don't care about cc2 or
cc3.
This reduces the traffic on the cc.php.net mirror and now delegates
much better between all the mirrors.
-Hannes