Comments (9)
Not dumb at all. The call:started
event is related to when two parties have established a P2P connection to each other. I think you are probably looking for the plain old connected
event if you are wanting an indication of when quickconnect has established connectivity with the signalling server.
The id, however, isn't reported in this event as it is assigned on the client prior. It should be available with the following code:
quickconnect('http://rtc.io/switchboard/', opts)
.on('connected', function() {
console.log('talking to the signalling server, and my id is: ' + this.id);
})
.on('call:started', function(id, pc, data) {
console.log('we have a new connection to: ' + id);
});
from rtc-quickconnect.
Muchas gracias, clears up my misconceptions.
from rtc-quickconnect.
Would be worth adding this to the documentation of the events.
I can't see that event mentioned at https://github.com/rtc-io/rtc-quickconnect/blob/master/docs/events.md
from rtc-quickconnect.
I really wanted to avoid duplicating the information. There's a link to the signaller events in the opening sentence in that events documentation, maybe I just need to make that more obvious to draw peoples attention to it..
from rtc-quickconnect.
My bad. Yet again I missed that link! Sorry.
from rtc-quickconnect.
As someone who has been bumbling around, I have found the documentation quite fragmented and difficult to get a toe-hold on. I'm sure much of this can be put down to my inexperience with the npm/node ecosystem, and I completely agree with not duplicating information.
I think a beefier documentation presence on rtc.io itself would be a welcome addition in helping get started (especially if it was generated from/included everything from github docs and had some higher order glue that showed how the various modules piece together). If I can help with anything on this front, just lemme know.
from rtc-quickconnect.
Completely agree Clinton. We've been slowly trying to do that and have a full redux of the rtc.io site planned to address this.
Unfortunately, I'm completely tainted by the node / browserify ecosystem so like to document things at a package level, but we've now got others on the team now that are helping us bridge the gap to the untainted :)
from rtc-quickconnect.
It's somewhat there on http://rtc.io/modules.html, but I agree it's fragmented. We should probably pull the information together without having to do click-throughs.
from rtc-quickconnect.
I agree that it is probably just a navigation thing (or my inexperience), once I find what I'm looking for it is outstanding.
from rtc-quickconnect.
Related Issues (20)
- Unable to connect to peer outside of local network
- Targetting new datachannel to particular end host
- requestChannel fails to register new data channel initiated from peer
- phantom data channels created on peer page reload/reconnect
- dependency install failure - utf-8-validate HOT 10
- TypeError: PeerConnection is not a function HOT 3
- Trying to connect to socket.io server throws " Connection closed before receiving a handshake response"
- Announce contains the user id of the person starting the call not who is announcing HOT 2
- On 3 way call the number of messages sent to signaller server increases at least 4 times until it stabilizes or fails HOT 2
- Ignoring messages that are not directed to each participant in a call is required when broadcasting to a room HOT 4
- `stream:added` can be emitted more than once for a stream
- Existing users will re-announce when any user in that room disconnected HOT 2
- Does increasing the heartbeat time increase the likelihood of getting "call expired" events?
- RTCPeerConnection object not clearing after participant leaves HOT 9
- Small grammatical errors in docs
- Failed to set remote offer sdp HOT 2
- Change room name on an existing rtc-quickconnect instance HOT 3
- Adapter.js throws an exception when removeStream is called HOT 6
- Failed to execute 'removeTrack' on 'RTCPeerConnection': parameter 1 is not of type 'RTCRtpSender HOT 1
- XML Parsing Error: no root element found
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rtc-quickconnect.