Re: [rtcweb] URIs for rtcweb "calls"

["Timothy B. Terriberry" <[e-mail]>]

> For the case where you are setting up something closer to a
> web-chat-with-an-agent-for-the-ad-seen here, I think the amount of
> page context will be very small, and that it will be closer to the
> experience of the browser/app setting up its default widgets for this.

I think over time there will be a desire to include more and more page 
context in such things. But that aside, it becomes a lot less clear to 
me what kind of default widgets would be. For the simple case of 1 audio 
+ 1 video stream, things are reasonably straightforward, but once you 
start talking about local preview, multiple video streams, layout and 
audio panning for conferencing, negotiating new streams in the middle of 
a call, and all the other things which people have been considering in 
the use cases here, there's a fair bit of complexity that a "default" 
widget set has to handle, compared to, say, creating a default <video> 
tag to wrap an URL that points directly at a WebM file. Web site authors 
are likely to have a much easier time handling this complexity, as they 
understand the context of what they're providing and can make 
simplifying assumptions, and present things in a coherent way (tying 
identity to video windows, etc.), but a generic widget set doesn't have 
that luxury, unless we explicitly limit the scope of what it is required 
to support.