On Tue, Mar 15, 2016 at 11:19 PM, Gomer Thomas
wrote:
> According to IETF RFC 7230 all HTTP recipients “MUST be able to parse the
> chunked transfer coding”. The logical interpretation of this is that
> whenever possible HTTP recipients should deliver the chunks to the
> application as they are r
Dear Colleagues,
The XHR specification has one very unsatisfactory aspect. It appears that
W3C and WHATWG are snubbing your noses at IETF.
According to IETF RFC 7230 all HTTP recipients "MUST be able to parse the
chunked transfer coding". The logical interpretation of this is that
whenever possi
On 16/03/2016 04:46, Richard Maher wrote:
...
Anyway, if the decorum police will agree to stay their truncheons for a
moment longer and indulge my use of satire, parody, and metaphor, in
making an extremely valid technical point,
...
Or you could just make your valid technical point, without re
Hi Léonie,
Please don't send spam about your HTML fork to this mailing list; we were
promised the WG merge would not cause our time to be wasted with that crap.
Thanks
Ms2ger
On Tue, Mar 15, 2016 at 11:39 PM, Léonie Watson wrote:
> Hello,
>
> There will be an HTML editors meeting on 10 - 11 Ma
On Wed, 16 Mar 2016, 04:46 Richard Maher, wrote:
> Look Jake, your entire argument is premised on the abstract notion that
> “cached
> data is often fine”. Allow me to respond with an equally unquantifiable
> “EXCEPT WHEN IT BLOODY ISN’T”.
>
> ...
>
> *The Bud Fox Day-Trader App*
>
> * …*
>
> W
