On Thu, Dec 8, 2011 at 2:36 PM, Charles Pritchard <ch...@jumis.com> wrote:
> > > > > On Dec 8, 2011, at 1:04 PM, Wenbo Zhu <wen...@google.com> wrote: > > > > On Wed, Dec 7, 2011 at 6:04 PM, Charles Pritchard < <ch...@jumis.com> > ch...@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? > Streaming request or response does not imply bi-directional messaging, i.e. the (non-RPC) semantics of WebSocket. > 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? > See below. > > > >> >> 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. > Not sure about the status of this spec. My original email merely tries to show the need to process/post data locally ... http://developers.whatwg.org/video-conferencing-and-peer-to-peer-communication.html#video-conferencing-and-peer-to-peer-communication > > > 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 >> >> >> >
