Do you know of any discussion or work to support Metalink in the
Apache Traffic Server [1] caching proxy?
I found this Google Summer of Code idea [2] ("Metalink integration
with Proxy/Cache" heading) for intermediate caching proxies to support
Metalink
And I found these two related Metalink discussion threads [3] [4]
I think a minimum viable product would add support for RFC 6249:
1. If the response status code is 3XX
2. Scan "Link: <...>; rel=duplicate" headers for URL that already
exist in the cache
3. If found, update "Location: ..." header with this URL and pass on
response
I volunteer here at the Agahozo-Shalom Youth Village in Rwanda. We use
Apache Traffic Server to overcome slow/unreliable downloads (and save
bandwidth). But because many sites distribute the same files from
different mirrors, it's frustrating for users to predict whether a
download will be fast (cache hit) or slow (cache miss). Following the
same link may be fast one time and slow the next
I think Apache Traffic Server could achieve better user experience (in
some cases) by implementing RFC 6249
[1] http://trafficserver.apache.org/
[2] http://sourceforge.net/apps/trac/metalinks/wiki/GsocIdeas
[3]
http://groups.google.com/group/metalink-discussion/browse_thread/thread/b59e5d99cf879529/f364acba525c7108
[4]
http://groups.google.com/group/metalink-discussion/browse_thread/thread/1849486ced99e778/7c2afbe0f3f8c41
--
You received this message because you are subscribed to the Google Groups
"Metalink Discussion" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/metalink-discussion?hl=en.
