W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [XHR] chunked requests

From: Charles Pritchard <chuck@jumis.com>
Date: Thu, 8 Dec 2011 14:36:25 -0800
Message-Id: <53A88FB3-BC42-4CEF-BBCE-8FFE6EF0B38F@jumis.com>
Cc: WebApps WG <public-webapps@w3.org>, Ian Hickson <ian@hixie.ch>
To: Wenbo Zhu <wenboz@google.com>




On Dec 8, 2011, at 1:04 PM, Wenbo Zhu <wenboz@google.com> wrote:

> 
> 
> On Wed, Dec 7, 2011 at 6:04 PM, Charles Pritchard <chuck@jumis.com> wrote:
> I think the Web Sockets spec is intended for client to server sessions like this.
> WebSocket protocol isn't yet well-supported by proxies. Besides, all we need here is a throwaway RPC-like request/response, and it's a bit heavy duty to use WebSocket for this use case. 
> 

Isn't a chunked stream the anti-thesis of RPC? It looks like you're acknowledging WebSockets works while asking about what to do with current web infrastructure. It seems to me that current infrastructure is -mostly- Flash based and assumes a level of control over input: one can't send arbitrary information as a developer.. It has to be directly from a webcam or similar media stream.

Do you have specific examples of existing infrastructure you're hoping to support?


>  
> 
> As for the peer-to-peer communication, I imagine the WebRTC group is where you'll see more activity on this issue.
> WebRTC is mostly peer-to-peer UDP (e.g. RTP), and the client-to-client communication has nothing to do with either HTTP or WebSocket. 


And MediaStream/Stream, which has to so with your request.


> 
> I don't know that arbitrary binary data is on their agenda -- I hope it is -- for p2p communication.
> 
> 
> 
> On 12/7/11 5:59 PM, Wenbo Zhu wrote:
>> 
>> One use case that we have which is not currently handled by XMLHttpRequest is incrementally sending data that takes a long time to generate _from the client to the server_. For example, if we were to record data from a microphone, we couldn't upload it in real time to the server with the current API.
>> 
>> The MediaStreaming spec also mentioned several use cases which would require streaming request data via an API:
>> - Sending the locally-produced streams to remote peers and receiving streams from remote peers.
>> - Sending arbitrary data to remote peers.
>> 
>> http://www.whatwg.org/specs/web-apps/current-work/multipage/video-conferencing-and-peer-to-peer-communication.html
>> 
>> - Wenbo
> 
> 
Received on Thursday, 8 December 2011 22:37:03 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:49 GMT