Re: Alternative to the offer/answer mechanism

On 20 June 2013 10:37, cowwoc <> wrote:
>     We need an API that lies somewhere between WebRTC and CU-RTCWEB because
> it looks like the latter complicates common use-cases. If you disagree, can
> you please reply with a complete testcase demonstrating what a common
> use-case would look like?

The CU-RTC-Web code samples show that it's very easy to establish a
simple audio call.  Complexity of the simplest scenarios are on-par
with RTCPeerConnection.  A more complicated example is shown here:
(look at the second example, not the first)

Received on Thursday, 20 June 2013 21:13:59 UTC