On Fri, 2012-08-03 at 11:33 +0200, W-Mark Kubacki wrote: > Brian, thanks for the stats and the pointer to layman. I guess we both > see the opportunity to share some experiences and code. Layman can > benefit from adding compression and I need to integrate your notices > about Py2/Py3 compatibility. > I haven't quite gotten all that is needed for py2/py3 compatibility done. Also I could not get it to work with both py2 and py3 with the same code. I have a little more to modify for a clean 2to3 run on the code to work without additional patching. > If it is okay with Zac I will refactor and improve the URL-fetching some > more. Following redirects, a proper auth-handler and 'identificator' > comes to mind. You could copy the final handlers, then. > :) my laziness thanks you in advance > Portage's 'emerge' currently contacts remote hosts whenever it is run > and this adds a noticeable delay. In the best case even the 304 (not > modified) responses are avoid wherever possible. So in the end success > of Portage's caching will not be measurable by a 200-to-304 ratio. > Layman does similar, but not every run, just -L, -f, -S, -s options, which is why I added the headers... hmm, adding the if >=x time fetch skip is a good idea. -- Brian Dolbec