[Nice] Change NiceComponentState to NICE_COMPONENT_STATE_READY

[Youness Alaoui]

Hi,

The state of the component should go to READY shortly after it goes to
CONNECTED. It's only waiting for any other pending connectivity checks to finish
before it decides which candidate pair it will use.
If that doesn't work, then please send a log so I can see what's causing it not
to go to READY.

I hope this helps,
Youness.

On 08/20/2013 02:41 AM, Ashish Gupta wrote:
> Hi.
> 
> I'm currently working to implement FT support in Pidgin for GTalk. I was stuck
> at traversing the NAT for a long time but then libnice came to the rescue :D
> 
> I can successfully enumerate my local candidates and send them to the peer on
> the other side using XMPP. The problem is, that as the remote candidates are
> received and added/updated on the NiceAgent, the state of the associated
> component goes to either NICE_COMPONENT_STATE_CONNECTED or _FAILED.
> 
> Since I basically want to write/read to a channel , I'm listening to the
> "reliable-transport-writable" signal so that I can proceed with sending GET
> requests on HTTP.
> 
> I've gone through the documentation and as far as I could understand, the
> "reliable-transport-writable" signal will be emitted once the _READY state is
> achieved.
> 
> Any ideas on how I could tackle this problem?
> 
> Since the _CONNECTED state means that at least one usable candidate pair was
> found, is it possible to somehow "force" the state to _READY and use the same
> candidate pair?
> 
> Thanks a lot,
> 
> Regards,
> Ashish Gupta
> 
> 
> 
> _______________________________________________
> nice mailing list
> nice at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/nice
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/nice/attachments/20130823/29c3ad88/attachment.pgp>