WebRTC Presentation

Presentation about WebRTC I gave to the Dundee Software Society on 3rd July 2014

Transcript

1. The Software Society July 2014
2. Who am I Paul Sutherland Construction Surveyor at Black & Veatch Moved across to application deployment Working on mobile app development Member of Software Society since its formation in 2011 mail@paulsutherland.net
3. WebRTC What it is How you can use it Technical challenges Browser woes
4. Motivation Dive in to understand what the technology is Do a talk to bring everyone here up to speed Use it in my web projects Have fun with leading edge technology
5. Let's Get in our Time Machine Back to 1994ish
6. When the web was young
7. When the web was a hypertext driven page centric design
8. Things were simple looking
9. Moving forward 1998
10. We were still dominated by page centric design
11. Early Amazon 2001
12. Early Amazon - no targeted ads!!
13. Even in 2003 it was still fairly static
14. Then through the early to mid 2000s we became dynamic
15. The term "Web 2.0" was first used in January 1999 by Darcy DiNucci
16. "The Web we know now, which loads into a browser window in essentially static screenfuls, is only an embryo of the Web to come. The first glimmerings of Web 2.0 are beginning to appear, and we are just starting to see how that embryo might develop. The Web will be understood not as screenfuls of text and graphics but as a transport mechanism, the ether through which interactivity happens. It will [...] appear on your computer screen, [...] on your TV set [...] your car dashboard [...] your cell phone [...] hand-held game machines [...] maybe even your microwave oven". https://en.wikipedia.org/wiki/Web_2.0
17. Web 2.0
18. We we are interacting with the data without chasing links
19. We start to feed the machine
20. Giving birth to the Social web
21. What Next?
22. Welcome to the Real Time Web
23. A world where through the browser you can: Share Files Live Chat Sensor Feeds Data Feeds Screen Sharing Gaming
24. All Peer to Peer
25. History Google purchase Global IP Solutions (GIPS) for $68m in 2010 Google release WebRTC as a proposed standard in June 2011 They have pushed the W3C and IETF to develop standards Ericsson Labs release a prototype
26. First Implementation https://labs.ericsson.com/developer-community/blog/beyond-
27. This is made possible using three APIs MediaStream RTCPeerConnection RTCDataChannel
28. MediaStream Obtains the audio and video tracks Captures them as separate tracks Combines both the tracks to form a stream You interact via navigator.getUserMedia();
29. MediaStream http://dev.w3.org/2011/webrtc/editor/getusermedia.html
30. getUserMedia() http://dev.w3.org/2011/webrtc/editor/getusermedia.html
31. getUserMedia() Example http://webcamtoy.com/app/
32. getUserMedia() Example http://idevelop.ro/ascii-camera/
33. getUserMedia() Example http://shinydemos.com/facekat/
34. Constraints getUserMedia takes constraints Determining the width and height of video Chrome allows screen capture (experimental)
35. RTCPeerConnection Communicating with other browsers Signal processing Sets up the peer to peer communication Handles security
36. RTCPeerConnection http://www.WebRTC.org
37. RTCDataChannel Uses RTCPeerConnection to send data This is in the form of JSON This can support gaming This can handle file transfers
38. RTCDataChannel Uses a websocket style of API Low latency Sent as reliable or unreliable data
39. RTCDataChannel Example https://www.sharefest.me/
40. How do we find a Browser NATs and Firewalls cause problems Difficult to obtain a public IP
41. STUN & TURN Stun can determine the public IP address of a browser Simple server which connects browsers peer to peer Google have released the source code for their STUN servers Images on Amazon available Stund package is available for Ubuntu
42. STUN server http://www.html5rocks.com/
43. TURN TURN server is the back up Relays the connection is peer to peer fails Seamless in the background determining STUN or TURN
44. TURN server http://www.html5rocks.com/
45. Managing STUN and Turn
46. Welcome ICE Managing the best connection rests with the ICE framework Figures out the best option for the call Utilises STUN as first resort
47. Security http://io13webrtc.appspot.com/#55
48. Browser Support Chrome 23 Firefox 22 Opera 18
49. Mobile Support Chrome 28 Firefox 24 Opera Mobile 12
50. Apple Not supporting it They are very silent on it They would need to replace the VP8 codec with H.264 Replace Opus voice codec with AAC-LD
51. Microsoft Have an alternative called CU-RTC-Web Stands for: Customizable, Ubiquitous Real-Time Communication Looking at a lower level API
53. Interoperability between browsers Firefox Beta post May 2013 Opera 20 Chrome 25 are interoperable
54. API Differences W3C Standard Chrome Firefox getUserMedia webkitGetUserMedia mozGetUserMedia RTCPeerConnection webkitRTCPeerConnection mozRTCPeerConnection RTCSessionDescription RTCSessionDescription mozRTCSessionDescription RTCIceCandidate RTCIceCandidate mozRTCIceCandidate
57. Outside the Browser sipML5 open source JavaScript SIP client Phono open source JavaScript phone API Zingaya embeddable phone widget
58. Demo http://zebibyte.co.uk
59. Hello Firefox, this is Chrome calling!