Re: Multi-server HTTP

I don't think so; 'alternate' doesn't specify for what purpose it's an  
alternate, and you need a very precise definition (byte-for-byte  
equivalence of representations). 'alternate' is often used to mean  
"here's a copy in another format" and similar.

Perhaps you should mint 'duplicate'...

Cheers,


On 29/08/2009, at 4:01 AM, Anthony Bryan wrote:

> On Fri, Aug 28, 2009 at 11:27 AM, Henrik
> Nordstrom<henrik@henriknordstrom.net> wrote:
>> fre 2009-08-28 klockan 12:38 +0100 skrev Ford, Alan:
>>
>> * Define a new Mirror profile object, similar to MetaLink but  
>> defining
>> the mirror URL policy for groups of URLs on the server, without going
>> into checksums etc (HTTP will give those).
>>
>> * Instance-Digest header returning the object checksum
>
> My connection has been down for a few days but here are my very rough
> ideas on doing Metalink in HTTP headers with the Link header, Instance
> Digests, and perhaps Content-MD5.
>
> Briefly, it's:
>
>   Link: <http://www2.example.com/example.ext>; rel="alternate";
>   Link: <ftp://ftp.example.com/example.ext>; rel="alternate";
>   Link: <http://example.com/example.ext.torrent>; rel="describedby";
>   type="torrent";
>   Link: <http://example.com/example.ext.asc>; rel="describedby";
>   type="application/pgp-signature";
>   Digest: SHA=thvDyvhfIqlvFe+A9MYgxAfm1q5=
>
> http://www.ietf.org/id/draft-bryan-metalinkhttp-00.txt
>
> I've been meaning to ask Mark Nottingham if "alternate" from Link
> header fits what we are using it for, to mean identical, duplicate
> copy, etc?
>
>   The Link Relation Type registry's initial contents are:
>
>   o  Relation Name: alternate
>   o  Description: Designates a substitute for the link's context.
>   o  Reference: [W3C.REC-html401-19991224]
>
>
> -- 
> (( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
>  )) Easier, More Reliable, Self Healing Downloads


--
Mark Nottingham     http://www.mnot.net/

Received on Monday, 31 August 2009 07:40:14 UTC