[rtcweb] Usecases for innovation.

[Tim Panton <[e-mail]>]

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.