Re: [RFC] helping smart-http/stateless-rpc fetch race

Heya,

On Mon, Aug 8, 2011 at 19:13, Junio C Hamano [off-list ref] wrote:

quoted

 (1) It might make sense to give admins who run upload-pack not behind
     smart-http an option to allow fetching from a non-tip; and

You said earlier it isn't needed since the server process caches the
refs for git and ssh, that leaves dumb-http right? If that is indeed
the case I think we can just argue that since smart-http is our
solution to the http problems, if admins want to make life easier for
http fetches on busy repositories they should be using smart-http.

quoted

 (2) It also might make sense to let admins who do run upload-pack behind
     smart-http force re-fetching when the race is encountered.

This would mean that if you're running smart-http without this option
enabled (because, say, you don't know it exists), your users have to
re-fetch (a lot). The only upside would be that if the server _knows_
what the user is asking for is outdated, that the user will know this
right away. That doesn't fly though, since we allow exactly that for
git and ssh transfer.

-- 
Cheers,

Sverre Rabbelier