Mailinglist Archive: zypp-devel (57 mails)
| < Previous | Next > |
Re: [zypp-devel] Read all patterns in 'one go'
- From: Stephan Kulow <coolo@xxxxxxx>
- Date: Tue, 22 Jan 2008 08:59:12 +0100
- Message-id: <200801220859.13386.coolo@xxxxxxx>
Am Dienstag 22 Januar 2008 schrieb Cristian Rodríguez:
layer on top of libcurl that redirector users can use and then we replace
libcurl usage with that code.
I don't think libzypp is the only code that could use some nice to use
wrapper that knows about the implications of our infrastructure.
Greetings, Stephan
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
Michael Matz escribió:I suggest you get your head together with Peter Poeml and write some
Downloading many small files over http is much worse then downloading
just one bigger one (and of course the bigger one compresses better).
and is even worst in the current situation because zypp floods the
servers with unneded requests or even (partial|complete) downloads
instead of using CURL_TIMECOND_IFMODSINCE , when I analyzed this issue I
was unpleasantly surprised with this misbehaviuor and I still dont know
why such a basic thing like being friendly with the mirrors and use less
network resources as possible was not considered in the current
implementation ;(
i.e last time I checked, a file exists check in zypp consisted in a
partial,small file download.. and almost any protocol supported by curl
have a way to do such operation without downloading any file..
layer on top of libcurl that redirector users can use and then we replace
libcurl usage with that code.
I don't think libzypp is the only code that could use some nice to use
wrapper that knows about the implications of our infrastructure.
Greetings, Stephan
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |