Re: Proposal for "fetch-any-blob Git protocol" and server design

2017-04-26 Thread Jonathan Tan
On 04/21/2017 09:41 AM, Kevin David wrote: Hi Jonathan, Sorry for the delayed response - other work got in the way, unfortunately! No worries! I am envisioning (1a) as described in Jeff Hostetler's e-mail [1] ("a pre-command or hook to identify needed blobs and pre-fetch them before

RE: Proposal for "fetch-any-blob Git protocol" and server design

2017-04-21 Thread Kevin David
Hi Jonathan, Sorry for the delayed response - other work got in the way, unfortunately! Kevin -Original Message- From: Jonathan Tan [mailto:jonathanta...@google.com] Sent: Thursday, April 13, 2017 4:13 PM >> I know we're considering server behavior here, but how large do you generally

Re: Proposal for "fetch-any-blob Git protocol" and server design

2017-04-13 Thread Jonathan Tan
On 04/12/2017 03:02 PM, Kevin David wrote: Hi Jonathan, I work on the network protocols for the GVFS project at Microsoft. I shared a couple thoughts and questions below. Thanks for your reply! I know we're considering server behavior here, but how large do you generally expect these

RE: Proposal for "fetch-any-blob Git protocol" and server design

2017-04-12 Thread Kevin David
nta...@google.com>; Ben Peart <peart...@gmail.com> Cc: git@vger.kernel.org; Mark Thomas <mar...@efaref.net>; Jeff Hostetler <g...@jeffhostetler.com> Subject: Re: Proposal for "fetch-any-blob Git protocol" and server design +cc Ben Peart, who sent "[RFC] Add support for d

Re: Proposal for "fetch-any-blob Git protocol" and server design

2017-03-28 Thread Stefan Beller
+cc Ben Peart, who sent "[RFC] Add support for downloading blobs on demand" to the list recently. This proposal here seems like it has the same goal, so maybe your review could go a long way here? Thanks, Stefan On Tue, Mar 14, 2017 at 3:57 PM, Jonathan Tan wrote: > As

Re: Proposal for "fetch-any-blob Git protocol" and server design

2017-03-16 Thread Jonathan Tan
On 03/16/2017 02:17 PM, Junio C Hamano wrote: Yeah, the example was solely to see how the system was to be extended, as one of the selling point of the proposal was: > === Endpoint support for forward compatibility > > This "server" endpoint requires that the first line be

Re: Proposal for "fetch-any-blob Git protocol" and server design

2017-03-16 Thread Junio C Hamano
Jonathan Tan writes: > On 03/15/2017 10:59 AM, Junio C Hamano wrote: >> ... >> but I am wondering how you would extend the proposed system to do >> so. Would you add "fetch-size-limited-blob-in-tree-pack" that runs >> parallel to "fetch-blob-pack" request? Would you

Re: Proposal for "fetch-any-blob Git protocol" and server design

2017-03-16 Thread Jonathan Tan
On 03/15/2017 10:59 AM, Junio C Hamano wrote: By "SHA-1s for which it wants blobs", you mean that "want" only allows one exact blob object name? I think it is necessary to support that mode of operation as a base case, and it is a good starting point. When you know - you have a "partial"

Re: Proposal for "fetch-any-blob Git protocol" and server design

2017-03-15 Thread Junio C Hamano
Jonathan Tan writes: > == Design > > A new endpoint "server" is created. The client will send a message in > the following format: > > > fbp-request = PKT-LINE("fetch-blob-pack") > 1*want > flush-pkt > want = PKT-LINE("want" SP obj-id) >

Proposal for "fetch-any-blob Git protocol" and server design

2017-03-14 Thread Jonathan Tan
As described in "Background" below, there have been at least 2 patch sets to support "partial clones" and on-demand blob fetches, where the server part that supports on-demand blob fetches was treated at least in outline. Here is a proposal treating that server part in detail. == Background