On 5/17/07, Matthieu Moy <Matthieu.Moy@xxxxxxx> wrote:
FYI, bzr uses HTTP range requests, and the introduction of this feature lead to significant performance improvement for them (bzr is more dumb-protocol oriented than git is, so that's really important there). They have this "index file+data file" system too, so you download the full index file, and then send an HTTP range request to get only the relevant parts of the data file.
That's the kind of thing I was imagining. Between the index and an additional "index-supplement-for-dumb-protocols" maintained by update-server-info, http ranges can be bent to our evil purposes. Of course it won't be as network-efficient as the git proto, or even as the git-over-cgi proto, but it'll surely be server-cpu-and-memory efficient. And people will benefit from it without having to do any additional setup. It might be hard to come up with a usable approach to http ranges. But I do think it's worth considering carefully. cheers, m - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
