On Thu, 5 Jan 2006 [EMAIL PROTECTED] wrote:
STUN's new structure starts to be stabilized. I just updated CVS to
Here's a few issues I've noted when I've ported the farsight-netsocket code to the latest API release.
1. stun_handle has the information of the TLS and UDP sockets, su_root etc. It also contains the list of stun_requests.
Hmm, I'm slightly confused about the callback implementation of stunc.c. The su_root_break() thingie is used for all events... isn't processing supposed to continue without user intervention (i.e. not having to run su_root_run(root) multiple times).
Also, it should be documented somewhere (in stun.docs, or stunc_callback()) what the client is supposed to do with the different events (partially the same problem as with nua callbacks). Some of these are probably just informative signals (stun_bind*, others), while others require some action from the client (stun_tls_done).
Or actually, is stun_tls_done the only one requiring specific action (i.e. if you want to use msg-integrity, you must first wait for stun_tls_done, before issuing stun_handle_bind()). Am I on the right track?
Still, it would be good to document which events are triggered by which API calls (like stun_handle_bind() may lead to stun_bind_* events, and so on).
PS Also the TODO-list of stun.docs should be probably updated... :) -- under work: Sofia-SIP at http://sofia-sip.sf.net ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Sofia-sip-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
