Re: [rtcweb] Usecases for innovation.

Hmm ... both of these seem to work fine with the direction we are going....both require the W3C getMedia API to allow JS access to the data so it's more of a W3C issue than IETF but my read of the tea leafs is that is the direction W3C is going. At the TPAC meeting Opera bought up good use cases for this and they seemed to get a good reception that people wanted to solve them.  My recollection was there were only one or two people at IETF objecting to JS access to media ( and come to think of they were all fans of the "low level" API :-) For purpose of argument, one could imagine implementing the Kinect stereo correlation in JS and just using any two camera along with auto calibration of geometry. That would be cool....

On Nov 1, 2011, at 2:30 AM, Tim Panton wrote:

> I've repeatedly been asked for use-cases for innovative applications of webRTC
> to justify my contention that we should be providing a low-level framework,
> not an embedded legacy compatibility application.
> 
> It's a 'when did you stop beating your wife?' question, there is no good answer.
> By definition we don't know what innovative uses are yet, so we are reduced to
> guessing, which sounds unconvincing.
> 
> By chance, this weekend I was exposed to 2 innovative uses of real-time-communications
> in a browser that _won't_ fit in the current looking-over-its-shoulder scheme.
> 
> 1) H264 implementation in Javascript http://yfrog.com/nmng0z 
> 2) Kinect as an input device for a virtual receptionist in a real reception area
> 	(Voxeo's as it happens).
> 
> Neither of these are production ready - or indeed necessarily a good idea,
> but the fact that neither (minor) innovation fits at all into our brand new framework
> should give us pause for thought. (but given the pell-mell dash to be compatible
> with last century's deskphones I don't imagine it will).
> 
> Tim.
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb