remove multiple ready events.

[druuu]

fixes #87
fixes #85

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[druuu]

I signed it!

[googlebot]

CLAs look good, thanks!

[nitobuendia]

@druuu Thanks a lot for sending the PR. It looks good to me. I have made just one comment to understand your change.

@samdutton I have tested the changes and they seem to work. There are some issues related that you can read on the "Conversation" of the PR.

I was not able to reproduce the issues on the bugs though. However, the changes on index.js do make sense in theory to me.

[nitobuendia]

@druuu Was this causing issues too or what's the logic to change it?

[nitobuendia]

PS: It works; just want to be sure we are not changing more than we should.

[druuu]

@nitobuendia
the changes are made because it looks a bit confusing, here we go:

before the changes:
user1 joins, 'isinitiator' is set to true for user1.
user2 joins, 'isinitiator' is set to false for user2 and also peerconnection is established for user2
user2 sends READY event, now user1 peerconnection is created

After the changes:
user1 joins, 'isinitiator' is set to true for user1.
user2 joins, 'isinitiator' is set to false for user2.
user2 sends READY event, peerconnection is created for both user1 and user2.

So, it looks more simple in the second case.
If you dont want these changes, i can send you another PR, or you can just remove https://github.com/googlecodelabs/webrtc-web/blob/master/step-06/index.js#L45

thank you for these tutorials, they are really helpful and simple.