Re: [Turnserver-devel] turnserver status

[Sébastien V. <vi...@cl...>]

Hi Justin,

Justin Karneges a écrit :
> On Thursday 12 November 2009 07:46:16 Sebastien Vincent wrote:
>   
>> Sébastien Vincent a écrit :
>>     
>>> Justin Karneges a écrit :
>>>       
>>>> 4) I want to be able to modify the allowed credentials while turnserver
>>>> is running, without dropping any active TURN sessions.  Is there a way
>>>> to safely update turnusers.txt and have turnserver honor the change
>>>> without restarting the daemon?
>>>>         
>>> Not yet :(. It is not the first time someone asked for that so I will
>>> add it to the roadmap for the 0.3 release.
>>>       
>> Today I added initial credentials reload support in SVN revision 123. It
>> should keep all active TURN sessions.
>>     
>
> Great.
>
>   
>> So if you are interrested in this feature, please test it :).
>>     
>
> I did not look at the code, but how do I cause the reloading?
>
>   

via SIGHUP signal.

>> For the case of an active TURN session which account has been removed or
>> password changed, it can still relay channel-data and data from peers
>> until a TURN message is received (not an ChannelData) which will closes
>> the TURN session.
>>
>> Is this behavior acceptable for you or should the server destroys
>> accountless TURN sessions as soon as the credentials reload is done ?
>>     
>
> Probably it should destroy them for completeness sake.  The sessions will get 
> rejected at the next refresh anyway, and I can't see a reason why you'd want 
> the sessions to stay open "just a little longer after I remove credentials".
>
> More interesting would be a way to remove credentials but keep the sessions 
> alive forever.  For example, in XMPP we plan to have a way to query for the 
> credentials to use with an associated TURN server, and these credentials 
> could potentially be temporary.  However, the sessions created with those 
> credentials should not be temporary.
>
> I'm not sure of the best way to implement that, but one idea would be to have 
> an "expired" flag that could be set on an account.  An expired account would 
> not allow new allocations, but would allow refreshes and other activity as 
> normal.  And turnserver could purge the account when all sessions associated 
> with it are closed.
>
>   

Now the new behavior is destroy all accountless sessions immediatly. I 
will think about your proposal later.

Regards,
--
Sebastien Vincent

> -Justin
>
>