From: Junio C Hamano <junkio@cox.net>
To: Craig Schlenter <craig@codefountain.com>
Cc: git@vger.kernel.org
Subject: Re: Balanced packing strategy
Date: Sat, 12 Nov 2005 18:34:02 -0800 [thread overview]
Message-ID: <7vveyxcm3p.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <b6abcb70496730705046934973221b93@codefountain.com> (Craig Schlenter's message of "Sat, 12 Nov 2005 17:14:36 +0200")
Craig Schlenter <craig@codefountain.com> writes:
> Does the pack index file contain enough information to enable a client
> to send http byte range requests to grab individual objects from a pack?
> It does seem to store object offsets...
Yes, it is certainly doable; there is enough information. I am
not sure if it is worth the complexity, though.
Many objects are stored delitified, so your byte range requests
would return delta and base object name. After you read what
was returned and find out the base object name, you would need
to get it, which can be another delta against its base object.
This would make tangling a delta chain would become a serialized
sequence of requests.
next prev parent reply other threads:[~2005-11-13 2:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 13:04 Remove unneeded packs Marcel Holtmann
2005-11-12 13:13 ` Andreas Ericsson
2005-11-12 13:30 ` Marcel Holtmann
2005-11-12 22:02 ` Lukas Sandström
2005-11-12 22:13 ` Marcel Holtmann
2005-11-13 2:38 ` Junio C Hamano
2005-11-13 10:58 ` Lukas Sandström
2005-11-13 12:00 ` Sergey Vlasov
2005-11-13 12:07 ` Lukas Sandström
2005-11-13 12:20 ` Sergey Vlasov
2005-11-13 12:31 ` Lukas Sandström
2005-11-12 13:40 ` Craig Schlenter
2005-11-12 13:59 ` Balanced packing strategy Petr Baudis
2005-11-12 15:14 ` Craig Schlenter
2005-11-13 2:34 ` Junio C Hamano [this message]
2005-11-13 11:00 ` Petr Baudis
2005-11-13 20:06 ` Josef Weidendorfer
2005-11-13 23:13 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-11-14 5:03 Craig Schlenter
2005-11-14 10:24 ` Josef Weidendorfer
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=7vveyxcm3p.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=craig@codefountain.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).