Gentoo Archives: gentoo-portage-dev

From: Brian Dolbec <dolsen@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] [PATCH] portage: HTTP if-modified-since and compression
Date: Fri, 03 Aug 2012 15:06:50
In Reply to: Re: [gentoo-portage-dev] [PATCH] portage: HTTP if-modified-since and compression by W-Mark Kubacki
1 On Fri, 2012-08-03 at 11:33 +0200, W-Mark Kubacki wrote:
2 > Brian, thanks for the stats and the pointer to layman. I guess we both
3 > see the opportunity to share some experiences and code. Layman can
4 > benefit from adding compression and I need to integrate your notices
5 > about Py2/Py3 compatibility.
6 >
8 I haven't quite gotten all that is needed for py2/py3 compatibility
9 done. Also I could not get it to work with both py2 and py3 with the
10 same code. I have a little more to modify for a clean 2to3 run on the
11 code to work without additional patching.
13 > If it is okay with Zac I will refactor and improve the URL-fetching some
14 > more. Following redirects, a proper auth-handler and 'identificator'
15 > comes to mind. You could copy the final handlers, then.
16 >
18 :) my laziness thanks you in advance
20 > Portage's 'emerge' currently contacts remote hosts whenever it is run
21 > and this adds a noticeable delay. In the best case even the 304 (not
22 > modified) responses are avoid wherever possible. So in the end success
23 > of Portage's caching will not be measurable by a 200-to-304 ratio.
24 >
26 Layman does similar, but not every run, just -L, -f, -S, -s options,
27 which is why I added the headers...
29 hmm, adding the if >=x time fetch skip is a good idea.
31 --
32 Brian Dolbec <dolsen@g.o>


File name MIME type
signature.asc application/pgp-signature