Re: Draft of alternative JSEP API proposal

- Introduce a PeerConnection id that's included in every signaling
message to distinguish a locally produced signaling message from a
remotely produced one. (Section 4)

For the browser to

know if an offer or answer was created locally, each PeerConnection

instance is assigned an internal unique identifier that is also included

in the signaling message header (#1 above).


Thanks for the proposal. The above paragraphs suggest that the id has two purposes:

1)  to distinguish a local offer/answer from a remote one;

2)  to distinguish each PeerConnection object;

Could you elaborate on the format of the id, and how 1) is achieved based on the format?
Why do we need to support 2) as well?


Received on Tuesday, 27 March 2012 02:03:14 UTC