Mailinglist Archive: zypp-devel (148 mails)
| < Previous | Next > |
Re: [zypp-devel] [SoC-student] libzypp HTTP download failover
- From: "Dr. Peter Poeml" <poeml@xxxxxxx>
- Date: Mon, 31 Mar 2008 15:51:49 +0200
- Message-id: <20080331135149.GK13264@xxxxxxx>
On Fri, Mar 28, 2008 at 07:08:49PM +0000, Benji Weber wrote:
It seems that you (and Jan) think that the parsing might be complicated.
In fact, this is not the case. It requires nothing else than reading the
first line from the mirror list, and extracting the URL from it. The
mirror list is already sorted. The URL is the ready-made URL to go to.
Just like the client reads the server reply headers now, sees the
Location: header, grabs the URL from that and follows it, it would read
the mirror list, grab the URL from the first line, and follow it.
That's really all there is to it.
In case of an error then, it can simply try the next one.
You see?
(Of course there are more sophisticated things that the client *could*
do also, but that's all optional, and not required.)
Peter
--
"WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH
Research & Development
On 28/03/2008, Jan Kupec <jkupec@xxxxxxx> wrote:
Just a quick thought. Two things that cross my mind are:
1) the idea of downloading & parsing a mirror list for each file doesn't
sound appealing to me.
[...] Obviously > downloading and parsing a file list for every
request is not sensible, [...]
It seems that you (and Jan) think that the parsing might be complicated.
In fact, this is not the case. It requires nothing else than reading the
first line from the mirror list, and extracting the URL from it. The
mirror list is already sorted. The URL is the ready-made URL to go to.
Just like the client reads the server reply headers now, sees the
Location: header, grabs the URL from that and follows it, it would read
the mirror list, grab the URL from the first line, and follow it.
That's really all there is to it.
In case of an error then, it can simply try the next one.
You see?
(Of course there are more sophisticated things that the client *could*
do also, but that's all optional, and not required.)
Peter
--
"WARNING: This bug is visible to non-employees. Please be respectful!"
SUSE LINUX Products GmbH
Research & Development
| < Previous | Next > |