From: Ricardo Correia <gentoo-dev@wizy.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Proposal for an alternative portage tree sync method
Date: Tue, 22 Mar 2005 23:58:32 +0000 [thread overview]
Message-ID: <200503222358.32905.gentoo-dev@wizy.org> (raw)
In-Reply-To: <424033C7.701@gentoo.org>
On Tuesday 22 March 2005 15:03, Simon Stelling wrote:
> And where is the benefit beside mirrors don't need to have a running
> rsync? If it uses exactly the same algorithm for finding the
> differences, users won't download less.
>
As it was already mentioned, it works through HTTP.
But what I think is great is that a sync doesn't have to work on 110,000
files, instead it only works on 1 file sequentially.
As you perhaps know how disks work, this should be a lot faster.
And zsync can be even better, it's still in the early stages of development.
I see only benefits (even if we just compare it to emerge-webrsync) :)
But only through experimentation we'll be able to see the difference..
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-22 23:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 7:15 [gentoo-dev] Proposal for an alternative portage tree sync method Ricardo Correia
2005-03-22 12:45 ` Daniel Drake
2005-03-22 12:59 ` Paul Waring
2005-03-22 13:22 ` Francesco Riosa
2005-03-22 15:03 ` Simon Stelling
2005-03-22 14:39 ` Stroller
2005-03-22 23:58 ` Ricardo Correia [this message]
2005-03-22 23:58 ` Ricardo Correia
2005-03-23 11:15 ` Fabian Zeindl
2005-03-23 18:03 ` Marius Mauch
2005-03-22 13:55 ` Patrick Lauer
2005-03-22 15:19 ` Simon Stelling
2005-03-22 23:58 ` Ricardo Correia
2005-03-23 22:15 ` Nick Rout
2005-03-23 22:49 ` Ricardo Correia
2005-03-24 14:11 ` Karl Trygve Kalleberg
2005-03-25 7:57 ` Brian Harring
2005-03-26 12:45 ` Karl Trygve Kalleberg
2005-03-27 19:03 ` Brian Harring
2005-03-28 13:04 ` Petteri Räty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200503222358.32905.gentoo-dev@wizy.org \
--to=gentoo-dev@wizy.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox