git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git over webdav: what can I do for improving http-push ?

From
JHJan Hudec <bulb@ucw.cz>
Date
Jan 1, 2008, 20:23 UTC
Message-ID
<20080101202352.GA4295@efreet.light.src>
In-Reply-To
<m3myrpo1p0.fsf@roke.D-201>
On Tue, Jan 01, 2008 at 10:12:28 -0800, Jakub Narebski wrote:
Show 11 quoted lines
> Grégoire Barbier <gb@gbarbier.org> writes:
> 
> > I think that real HTTP support is better than all workarounds we
> > will be able to find to get through firewalls (when CONNECT is not
> > available, some awful VPNs that send Etherne over HTTP may work
> > ;-)).  That's why I'm ok to work several hours on git code to
> > enhance real HTTP(S) support.
> 
> There was also an idea to create a CGI program, or enhance gitweb
> to use for pushing. I don't know if it would be better way to pursue
> to work around corporate firewalls, or not...

It is what bzr and mercurial do and I think it would be quite good way to go for cases like this. Eg. while our corporate firewall does allow anything through connect on 443 (so I can use ssh that way), it does *not* support web-dav in non-ssl mode. So I eg. can't even get from public subversion repositories at work.

I have also thought about optimizing download using CGI, but than I thought, that maybe there is a way to statically generate packs so, that if the client wants n revisions, the number of revisions it downloads is O(n) and the number of packs it gets them from (and thus number of round-trips) is O(log(n)). Assuming the client always wants everything up to the tip, of course. Now this is trivial with linear history (pack first half, than half of what's left, etc., gives logarithmic number of packs and you always download at most twice as much as you need), but it would be nice if somebody found a way (even one that satisfies the conditions on average only) to do this with non-linear history, it would be very nice improvement to the http download -- native git server optimizes amount of data transfered very well, but at the cost of quite heavy CPU load on the server.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>
Previous: Jakub NarebskiNext: Grégoire Barbier
Message 7 of 14 in “git over webdav: what can I do for improving http-push ?”
  1. Grégoire BarbierDec 30, 2007
  2. Daniel BarkalowDec 31, 2007
  3. Graham BarrDec 31, 2007
  4. Jan HudecJan 1, 2008
  5. Grégoire BarbierJan 1, 2008
  6. Jakub NarebskiJan 1, 2008
  7. Jan HudecJan 1, 2008
  8. Grégoire BarbierJan 3, 2008
  9. Jan HudecJan 3, 2008
  10. Linus TorvaldsJan 3, 2008
  11. Jakub NarebskiJan 3, 2008
  12. Grégoire BarbierJan 3, 2008
  13. Martin LanghoffJan 3, 2008
  14. Jan HudecJan 4, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.