An element providing a starting point for your own reusable Polymer elements.
- When a user gives access to their stream, we start a peer connection
- Create User A's peerconnection with handler methods for stream and icecandidate events
- User B joins the room
- If this is User A (the one whos starts it) then we create an Offer to User B
- When User B gets the offer, we check if the peer connection from User B has been created, if it hasn't, we create it
- On User B's peer connection, we set the remote description to the description that was sent in the offer (User A's description)
- User B creates an answer to User A's offer which involves setting User B's localDescription and sending that in a message
- User A gets User B's message with its description then sets it to User A's remote Description
- When anyone enters the shop a buzzer sounds.
- Jack enters the shop and the buzzer sounds
- The shop is empty so Jack waits patiently.
- Jill enters the shop, again the buzzer sounds.
- Jack hears the buzzer, goes to the door and hands his business card to Jill.
- Jill looks at his business card and records the information to her phone.
- Jill then gives Jack her business card.
- Jack records her information in to his phone.
Representations
- Jack and Jill represent the two people in the call
- The buzzer represents the signaling server
- The business card represents the RTCSessionDescription
- The phone represents the RTCPeerConnection
Element dependencies are managed via Bower. You can install that via:
npm install -g bower
Then, go ahead and download the element's dependencies:
bower install
If you wish to work on your element in isolation, we recommend that you use Polyserve to keep your element's bower dependencies in line. You can install it via:
npm install -g polyserve
And you can run it via:
polyserve
Once running, you can preview your element at
http://localhost:8080/components/webrtc-channel/
, where webrtc-channel
is the name of the directory containing it.
Simply navigate to the /test
directory of your element to run its tests. If
you are using Polyserve: http://localhost:8080/components/webrtc-channel/test/
The tests are compatible with web-component-tester. Install it via:
npm install -g web-component-tester
Then, you can run your tests on all of your local browsers via:
wct
wct -l chrome
will only run tests in chrome.
wct -p
will keep the browsers alive after test runs (refresh to re-run).
wct test/some-file.html
will test only the files you specify.
If you'd like to use Yeoman to scaffold your element that's possible. The official generator-polymer
generator has a seed
subgenerator.