W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2011

Re: p1 7.2.4: retrying requests

From: Dzonatas Sol <dzonatas@gmail.com>
Date: Tue, 07 Jun 2011 08:59:37 -0700
Message-ID: <4DEE4AE9.6080101@gmail.com>
To: ietf-http-wg@w3.org
On 06/07/2011 12:02 AM, Mark Nottingham wrote:
> OK. Can you suggest things to add to or take away from the spec as it 
> sits?
>

Since "multiplexing" was brought up, then the Expect: limits that 
ability to just one status code. There would need to be something like 
an outer and inner Expect: with different code to denote the continue on 
current stream or something to wait for the token of another stream.

Consider this code (what clouds want, a.k.a. "otoy") with HTML5 <canvas>:

"""
var Canvas = require('canvas'), canvas = new Canvas(300, 300), ctx = 
canvas.getContext('2d'), fs = require('fs');
var out = fs.createWriteStream('example.png'), stream = 
canvas.createPNGStream();
stream.on('data', function(chunk) {  out.write(chunk); });
"""

That would allow chunked mode to act like frames. It's nice to have that 
mode supported for it's raw-ness. I think it may be more viable to 
script an X11 framebuffer in that chunked-stream rather than multiplex 
outside of that, otherwise mime-parts, XMPP, and now WebRTC already 
exist. The above code, however, exploits how javascript "expects" to 
control the connection state.

-- 
--- https://twitter.com/Dzonatas_Sol ---
Web Development, Software Engineering, Virtual Reality, Consultant
Received on Tuesday, 7 June 2011 16:01:53 GMT

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