On Fri, May 20, 2016 at 02:39:06PM +0200, Christian Couder wrote:
> I wonder if this mechanism could also be used or extended to clone and
> fetch an alternate object database.
>
> In [1], [2] and [3], and this was also discussed during the
> Contributor Summit last month, Peff says that he started working on
> alternate object database support a long time ago, and that the hard
> part is a protocol extension to tell remotes that you can access some
> objects in a different way.
>
> If a Git client would download a "$name.bndl" v3 bundle file that
> would have a "data: $URL/alt-odb-$name.odb" extended header, the Git
> client would just need to download "$URL/alt-odb-$name.odb" and use
> the alternate object database support on this file.
>
> This way it would know all it has to know to access the objects in the
> alternate database. The alternate object database may not contain the
> real objects, if they are too big for example, but just files that
> describe how to get the real objects.
I'm not sure about this strategy. I see two complications:
1. I don't think bundles need to be a part of this "external odb"
strategy at all. If I understand correctly, I think you want to use
it as a place to stuff metadata that the server tells the client,
like "by the way, go here if you want another way to access some
objects".
But there are lots of cases where the server might want to tell
the client that don't involve bundles at all.
2. A server pointing the client to another object store is actually
the least interesting bit of the protocol.
The more interesting cases (to me) are:
a. The receiving side of a connection (e.g., a fetch client)
somehow has out-of-band access to some objects. How does it
tell the other side "do not bother sending me these objects; I
can get them in another way"?
b. The receiving side of a connection has out-of-band access to
some objects. Some of these will be expensive to get (e.g.,
requiring a large download), and some may be fast (e.g.,
they've already been fetched to a local cache). How do we tell
the sending side not to assume we have cheap access to these
objects (e.g., for use as a delta base)?
So I don't think you want to tie this into bundles due to (1), and I
think that bundles would be insufficient anyway because of (2).
Or maybe I'm misunderstanding what you propose.
-Peff
--
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