Add comments about PeerConnection::Close and PeerConnectionObserver.

Add comments about PeerConnection::Close and PeerConnectionObserver.

Documenting that the observer can safely be destroyed after Close has
been called, because it ensures no more callbacks will be invoked. Just
like in JavaScript land, where no more events will be fired after
"close" is called.

This is already covered by unit tests.

BUG=webrtc:7491
NOTRY=True
TBR=pthatcher@webrtc.org

Review-Url: https://codereview.webrtc.org/2834543005
Cr-Commit-Position: refs/heads/master@{#17798}
Committed: https://chromium.googlesource.com/external/webrtc/+/d07061c9f3ac5b0514ba02376d5a3ef471d2638b

[Taylor Brandstetter, 2017-04-20 20:10:44]

deadbeef@webrtc.org changed reviewers:
+ pthatcher@webrtc.org

[Taylor Brandstetter, 2017-04-20 20:10:45]

PTAL - just a documentation change.

[Taylor Brandstetter, 2017-04-20 20:10:59]

Description was changed from

==========
Add comments about PeerConnection::Close and PeerConnectionObserver.

Documenting that the observer can safely be destroyed after Close has
been called, because it ensures no more callbacks will be invoked. Just
like in JavaScript land, where no more events will be fired after
"close" is called.

This is already covered by unit tests.

BUG=webrtc:7491
==========

to

==========
Add comments about PeerConnection::Close and PeerConnectionObserver.

Documenting that the observer can safely be destroyed after Close has
been called, because it ensures no more callbacks will be invoked. Just
like in JavaScript land, where no more events will be fired after
"close" is called.

This is already covered by unit tests.

BUG=webrtc:7491
NOTRY=True
TBR=pthatcher@webrtc.org
==========

[Taylor Brandstetter, 2017-04-20 20:16:02]

The CQ bit was checked by deadbeef@webrtc.org

[commit-bot: I haz the power, 2017-04-20 20:16:11]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2017-04-20 20:19:01]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1492719362660320, "parent_rev":
"492c09fe59064c5d49f9110ed9c638a5f8a016b4", "commit_rev":
"d07061c9f3ac5b0514ba02376d5a3ef471d2638b"}

[commit-bot: I haz the power, 2017-04-20 20:19:04]

Description was changed from

==========
Add comments about PeerConnection::Close and PeerConnectionObserver.

Documenting that the observer can safely be destroyed after Close has
been called, because it ensures no more callbacks will be invoked. Just
like in JavaScript land, where no more events will be fired after
"close" is called.

This is already covered by unit tests.

BUG=webrtc:7491
NOTRY=True
TBR=pthatcher@webrtc.org
==========

to

==========
Add comments about PeerConnection::Close and PeerConnectionObserver.

Documenting that the observer can safely be destroyed after Close has
been called, because it ensures no more callbacks will be invoked. Just
like in JavaScript land, where no more events will be fired after
"close" is called.

This is already covered by unit tests.

BUG=webrtc:7491
NOTRY=True
TBR=pthatcher@webrtc.org

Review-Url: https://codereview.webrtc.org/2834543005
Cr-Commit-Position: refs/heads/master@{#17798}
Committed:
https://chromium.googlesource.com/external/webrtc/+/d07061c9f3ac5b0514ba02376...
==========

[commit-bot: I haz the power, 2017-04-20 20:19:05]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/external/webrtc/+/d07061c9f3ac5b0514ba02376...