W3C home > Mailing lists > Public > www-talk@w3.org > January to February 2009

RE: host-meta file format comments (draft-nottingham-site-meta-01)

From: Eran Hammer-Lahav <eran@hueniverse.com>
Date: Wed, 11 Feb 2009 01:06:09 -0700
To: Thomas Roessler <tlr@w3.org>
CC: "www-talk@w3.org" <www-talk@w3.org>, Mark Nottingham <mnot@mnot.net>
Message-ID: <90C41DD21FB7C64BB94121FBBC2E7234127C939CC1@P3PW5EX1MB01.EX1.SECURESERVER.NET>


> -----Original Message-----
> From: Thomas Roessler [mailto:tlr@w3.org]
> Sent: Tuesday, February 10, 2009 5:06 PM
>
> BTW, I notice that this draft is silent on the HTTP header syntax's
> combining feature for multiple occurences of the same field (last
> paragraph of 4.2, RFC 2616); I suspect that to be one of the more
> likely causes for surprises if HTTP header parsers are re-used.  (No
> such risk with MIME parsers.)

It is somewhat implied since Link header supports it and the Link field uses Link header as-is. My upcoming Link-Pattern field also supports it.

> Finally, why disallow whitespace stuffed folding?  It's pretty useful
> to make long lines editable, and I suspect that we're assuming /host-
> meta to be the product of some human with emacs in their hands. ;-)
> Implementing it is easy, and a given if existing parsers are used.

I would actually like to be able to break long lines... it makes writing spec example much easier.

EHL
Received on Wednesday, 11 February 2009 08:06:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:30 GMT