[jitsi-dev] Ice Ice Baby


#1

The song, of course, is here?

https://youtu.be/rog8ou-ZepE?t=15

Is there a reason, however, that the CandidateType enum does not have a CandidateType of tcptype?


#2

CandidateType describes whether the candidate's address is on a local interface -- "host", is remote and we learned about it by consulting a server (e.g. STUN) -- "srflx", etc.

We have a separate CandidateTcpType for the additional "tcptype" attribute of TCP candidates (and a separate Transport for the transport protocol).

Boris

···

On 10/03/2017 10:01, John Hemming wrote:

The song, of course, is here?

https://youtu.be/rog8ou-ZepE?t=15

Is there a reason, however, that the CandidateType enum does not have a
CandidateType of tcptype?


#3

Thank you for this. However, what happens when parsing an SDP from somewhere else. Are different objects created? I don't have a real problem today with this, but I just wondered when looking at remote candidates what happens when they are tcptype (at the moment I ignore the tcptype ones).

···

On 13/03/2017 16:12, Boris Grozev wrote:

On 10/03/2017 10:01, John Hemming wrote:

The song, of course, is here?

https://youtu.be/rog8ou-ZepE?t=15

Is there a reason, however, that the CandidateType enum does not have a
CandidateType of tcptype?

CandidateType describes whether the candidate's address is on a local interface -- "host", is remote and we learned about it by consulting a server (e.g. STUN) -- "srflx", etc.

We have a separate CandidateTcpType for the additional "tcptype" attribute of TCP candidates (and a separate Transport for the transport protocol).

Boris

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

I don't know what you mean when you say remotes candidates which "are tcptype".

"tcptype" is a an additional attribute which candidates with protocol TCP have.

Boris

···

On 13/03/2017 12:40, John Hemming wrote:

Thank you for this. However, what happens when parsing an SDP from
somewhere else. Are different objects created? I don't have a real
problem today with this, but I just wondered when looking at remote
candidates what happens when they are tcptype (at the moment I ignore
the tcptype ones).