Tag Archive | orca

ORTC Live Demo at IIT RTC Expo


Last week marked the first time the ORTC API was demonstrated in public.  Bernard Aboba (Microsoft) was joined by Robin Raymond (Hookflash) as they demonstrated an early prototype built on the ORTC API at the IIT RTC Expo in Chicago.

Adalberto Foresti (Principal Program Manager, Microsoft Open Technologies, Inc.) had this to say about ORTC…

Microsoft Open Technologies has re-worked our previous prototype and demo code to use ORTC. The prototype demonstrates how to support H.264/AVC video without SDP, by building the appropriate JavaScript code and without introducing any changes in the relevant parts of the ORTC specification. To be very clear, this is a first stab at an implementation, and better/faster/more stable versions are upcoming. The main objective is to determine that the W3C ORTC spec is easily implementable on top of existing stacks and usable by real Web developers.

You can get involved by downloading the prototype here, or join the discussion in the W3C ORTC Community Group and contribute code to implementations in the ORTC GitHub repository. We’re interested in your feedback on how to best achieve the industry’s shared goals for web-based realtime communications in the browser.

Microsoft joined the ORTC community and fully supports the ORTC approach, which is very consistent with our original CU-RTC-Web proposal.

In conclusion, the realtime communications over the Web community is moving toward the shared goal of simple, reliable, plugin-free real-time communications in the browser, and this prototype is an important step in the journey. It’s a first step, and we’ll continue to work with the community to improve its functionality, performance and stability.

read more…

Join the W3C Community Group and help cultivate open web concepts in RTC models.

WebRTC Object API (alpha) – Request for Feedback

From the ORCA W3C community group…

WebRTC Object API (alpha):

Early example code, written in Node.js:

It is the current authors intent to provide an alternative to the existing WebRTC API, to allow more control to web developers looking to leverage WebRTC.

Rationale for this alternate approach can be found in the informational draft submitted to the IETF RTCWEB working group several weeks ago.

Those interested in assisting in the completion of this API reference are asked to join this community group and take part in the discussions by:

On behalf of the current authors, thank you for your support and consideration.

%d bloggers like this: