Re: [PATCH] Show URL in the "Getting <foo> list" http-fetch messages

On Sat, Nov 12, 2005 at 09:22:02AM -0800, Nick Hengeveld wrote:

This should not be an issue with index requests because they are only
initiated from fetch().  The previous patch to load alternates on demand
added alternate handling to process_curl_messages() so that a 404 for an
object can be handled immediately rather than waiting for the fetch()
call for that object to notice.

Seems like it might make sense to handle pack downloads immediately when
an object is unavailable rather than waiting for the fetch() call.  It
could prevent attempts to download any other objects inside that pack,
although queued requests that activate while a pack is downloading
would have to wait to see whether the download is successful.  If such
an object also exists loose it would prevent a redundant download and if
not it would at least prevent an unnecessary check and 404.

Thoughts?

-- 
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.