GitLab

TURN specs says it must be long term credentials. So the short term/long term credentials can be removed from the API, and we'll only use the compatibility to decide what method of authentication to use

We should not free the username/password used for authenticating until the candidate discovery is also freed, otherwise we can't authenticate the response

Correctly check for errors when processing TURN response and support long term credentials unauthorized message correctly

Fix checking for the remote candidate using the username, and correctly create the remote peer reflexive candidate

Removed g_debug messages and replaced with nice_debug, en/disable-able with nice_debug_en/disable API

Correctly set the priority for jingle and for msn compatibility (multiplied by 1000 so it can fit as an uint)

Porting libnice to the new stun usage API. I know it's a big commit, but it can't be divided into smaller ones, it's all one big chunk

Do not unlock the mutex when emitting the signal because it might unlock another thread which could cause a race condition.
To avoid a deadlock when a signal callback calls an API function that does a g_mutex_lock while the lock is already taken. Change the mutex into a recursive mutex

Make sure that candidate pairs are created correctly when the remote candidates were added before the local candidates were gathered. This is a threading race condition fix.

darcs-hash:20080426002910-3e2dc-36ef20ecb418dc080bd2f187fbf3ccb4122a5b14.gz

darcs-hash:20080425200042-3e2dc-84d2a1ba9a2ebec18d8700a15647a586957f4ce4.gz

darcs-hash:20080422205137-4f0f6-8911d8cc165b0298a3e009834fe2dbed68cc1ca1.gz

darcs-hash:20080422161414-4f0f6-388208b2ac7bb2a7ab06e48151e2152fc0621331.gz

darcs-hash:20080402185805-4f0f6-d575bacdd796be98b42597605baf21b24a331047.gz

darcs-hash:20071116154328-77cd4-c2438891dd541b57b8b892eb86cc5573dcfc8708.gz

darcs-hash:20071010114010-77cd4-5aba24bc8c7d56e01596b824c6d6d7c5a37a1d05.gz

darcs-hash:20070911172243-77cd4-ad1407a763afe2d14d3b7d41c09a8bc4d65c5f9c.gz