Re: RTCSession object

A minor comment. Does this map 1:1 to an RTP session? I don't think so but
if it doesn't then how about using a different name? RTCDialog? RTCContext?
RTCConnection? RTCPeerConnection?

Second, less minor, I understand the need for a default session and trying
to spare users from having to mess with it, but am a bit worried that one
default session per page might not work well. I am thinking about cases
where one page establishes connections with different peers. There are many
examples of this today.

So I am wondering if this shouldn't be a more obvious and mandatory part of
the API.

Thoughts?

--sent from my mobile