W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2009

Re: Multi-server HTTP

From: Anthony Bryan <anthonybryan@gmail.com>
Date: Thu, 17 Sep 2009 18:00:47 -0400
Message-ID: <bb9e09ee0909171500g6d291c59wba9223f9e546465b@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Nicolas Alvarez <nicolas.alvarez@gmail.com>, ietf-http-wg@w3.org
On Wed, Sep 16, 2009 at 2:55 AM, Mark Nottingham <mnot@mnot.net> wrote:
>
> On 15/09/2009, at 1:59 PM, Anthony Bryan wrote:
>
>> On Mon, Sep 14, 2009 at 11:06 PM, Mark Nottingham <mnot@mnot.net> wrote:
>>>
>>> On 08/09/2009, at 11:19 AM, Anthony Bryan wrote:
>>>
>>>> Here's what I have now. More inclusive is good but I think someone
>>>> else would be better at writing it than me.
>>>>
>>>> http://tools.ietf.org/html/draft-bryan-metalinkhttp
>>>>
>>>> Link Relation Type Registration: "duplicate"
>>>>
>>>>  o Relation Name: duplicate
>>>>  o Description: Refers to an identical resource that is a
>>>> byte-for-byte equivalence of representations.
>>>
>>> Does this imply that each resource has exactly the same set of
>>> representations, or that when two resources share representations, those
>>> representations are duplicates?
>>
>> The latter.
>>
>> Any suggestions for replacement text? Because what I have isn't cutting
>> it.
>
> Hm.
>
> Refers to a resource whose available representations are byte-for-byte
> identical with the corresponding representations of the context IRI.

Thank you, sir. Much appreciated.

http://tools.ietf.org/html/draft-bryan-metalinkhttp

For anyone interested, you can try out Metalink in HTTP headers w/ the
software from here:

http://metalinks.svn.sourceforge.net/viewvc/metalinks/checker/
http://metalinks.svn.sourceforge.net/viewvc/metalinks/webconvert/
(Python script to convert .metalink to Apache directives)

>>>> Here's what it looks like:
>>>>
>>>>  Link: <http://www2.example.com/example.ext>; rel="duplicate";
>>>>  Link: <ftp://ftp.example.com/example.ext>; rel="duplicate";
>>>>  Link: <http://example.com/example.ext.torrent>; rel="describedby";
>>>>  type="torrent";
>>>
>>> Do torrents have media types yet?
>>
>> Not as far as I know.
>>
>> Which is also why in draft-bryan-metalink we have this:
>>
>> 4.2.10.2. The "type" Attribute
>>
>>  metalink:metaurl elements MUST have a "type" attribute that indicates
>>  the MIME type of the metadata available at the IRI.  In the case of
>>  BitTorrent as specified in [BITTORRENT], the value "torrent" is
>>  required.  Types without "/" are reserved.  Currently, "torrent" is
>>  the only reserved value.
>
>
> Overloading type like that is bad; register a media type (or get the
> appropriate people to do it).

This was from Julian's comment:
http://www.ietf.org/mail-archive/web/apps-review/current/msg00155.html

BitTorrent uses "application/x-bittorrent". What would I register?
"application/vnd.bittorrent"?

Probably worse, current Metalink uses "application/metalink+xml" from
when we didn't know any better. Should I register something else?

-- 
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads
Received on Thursday, 17 September 2009 22:01:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:10 GMT