Re: Hash for Links [Was: Re: Posted PaceEnclosuresAndPix]

[Robert Sayre <mint@xxxxxxxxxxxxxxx>]

Bill de hÓra wrote:

> >  <link rel="enclosure" href="http://example.com/somefile.mp3";
> >          hash="{generated_hash_value}"          
> > hashalg="{uri_identifying_the_hash_algorithm_used" />
> >
> > The hash and hashalg attributes would be optional but MUST appear 
> > together.
> >
> > Thoughts? (If we have more than two people respond favorably to this,
> > I'll write up a Pace for it)
>
>
>
> Seems like a good idea - would it be possible to move them into elements?


Well, Content-Length lives in the attributes as "length", but I don't 
think we need to make a home for every HTTP header. Content-MD5 will 
work just fine; it would probably be wise to send a HEAD request before 
automatically downloading a giant mp3. Furthermore, you'll get a good 
enough identifier by concatenating the URI and the length. Something 
more accurate will require a HEAD request. Thirdly, there's absolutely 
no reason to have this in core.

Robert Sayre