[Typo3-typo3org] Concept for mirroring the TER
Jan-Hendrik Heuing [NF]
jh at netfielders.de
Tue Mar 8 15:55:11 CET 2005
Generaly this diff-thing sounds interesting, but I only think about
research, not about traffic. As you would increase server load by this,
while traffic is no problem in that dimension...
"Michael Stucki" <michael at typo3.org> schrieb im Newsbeitrag
news:mailman.1.1110271477.9883.typo3-team-typo3org at lists.netfielders.de...
> Ciao Roberto,
>> I just uploaded my draft for the mirroring concept to our team page .
>> Please comment on the general ideas at this list.
> Basically, this looks really good to me!
> Round robin: I'm not an expert with this but I guess that the DNS should
> alternate between IP addresses but CNAMES:
> => mycompany.mirrors.typo3.org
> => ch2.mirrors.typo3.org
> See below why this might be helpful to still reach a specific mirror.
> Why master repository? I think this is not needed at all. Why not have the
> Super Mirrors doing this? The required steps seem to be easy I guess:
> - Before uploading a new extension, the Super Mirror checks on all others
> this extension is known/availble by them (for solving conflicts)
> If found => redirect the client to this server for further processing.
> - If an extension is being searched and not found, one could run a "global
> search" in order to let the Super Mirrors look up at his
> Small detail:
> If you want to run the repository exactly like Debian, I suggest you use
> this structure:
> However I like this idea more:
> (If you don't want to add the version number twice, please at least make
> sure that the filename is being changed when sending HTTP headers.)
> How is typo3.org handling those different repositories? Will it fetch the
> data from its own (private) mirror?
> Why do you want to add possibility to limit traffic to a certain amount?
> I guess this makes it nothing but complicated. It would be much easier if
> the provider could just edit the mirror list and remove his name if he
> thinks it's enough.
> (If you have an easy solution for that problem, simply forget my
> comment ;-))
> Further ideas:
> Watch the above file system structure. If we add a special (not mirrored)
> subdirectory that holds the unpacked extension (e.g. "_unpacked") then we
> could easily provide a diff feature which lets you compare between
> versions. Would be very useful I guess!
> Kind regards,
> - michael
> Want support? Please read the list rules first:
> Time to subscribe to typo3-announce:
More information about the TYPO3-team-typo3org