[
Lists Home |
Date Index |
Thread Index
]
Simon St.Laurent wrote:
> robin.berjon@expway.fr (Robin Berjon) writes:
>>It is indeed. But there is no work that I know of going on around HTTP
>>so I'm unsure how much can be done.
>
> I don't think this work needs to happen in HTTP specifically - it seems
> like it could be broken out as a more general MIME-related issue. This
> kind of encoding seems useful in contexts way beyond HTTP.
I agree entirely, unfortunately it is currently spec'd as part of HTTP which
makes it hard to move around...
>>I've talked with IANA people about the registration of new content
>>codings (since they're in charge of it), and asked if adding
>>parameters would be ok. They kindly answered that they had to dig up a
>>very old form from some random location and that they had no idea.
>>Something in the kind tone suggested that they might as well have been
>>communicating with a perfect alien. Either way, a new content coding
>>needs to be a RFC -- which is where the issue would likely be banged
>>on -- so I had no chance to look further into it.
>
> You (or the W3C binary folks) might write up a trial balloon
> Internet-Draft and see where it goes. That's relatively easy and it
> would at least start the discussion, though it might be something that
> should proceed as part of the W3C Binary whatever work and probably in
> concert with the IETF/IESG/IANA folks.
Well... there currently are no "W3C Binary folks" (or "W3C Binary Infosets WG")
so let's not get too far ahead of ourselves ;) However that's pretty much the
plan I've been thinking about, it should be simple enough. I'm just waiting to
see if there will be "W3C Binary folks" or not since that'd carry more weight
than I alone.
>>>(I worry that other people will read it the way I did and start
>>>hacking encoding parameters into Content-Type rather than use
>>>Content-Encoding.
>>
>>But then we can point fingers and laugh at their bad taste.
>
> Doesn't tend to work.
Yes, yes, I know. I was just pointing out that *at least* we can laugh at it,
not counting on it having much effect.
--
Robin Berjon <robin.berjon@expway.fr>
Research Engineer, Expway http://expway.fr/
7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
|
