Hello, I've been wondering about this for a while. Having the cname in the base API in fs_conference_new_participant() was probably not a great idea. It seems that the various SSRCs can be associated with a stream using various techniques.
So I'd like to propose the following API change (since we're not officially API stable yet). Change fs_conference_new_participant(conf, cname, gerror) to be fs_conference_new_participant(conf, gerror). And let the cname be settable as a property of the RTP participant afterwards. Also, change the RtpSession to have a ssrc property to the ssrc its using can be known and add a message so the user is informed if it changes (in case of a collision). Also, also add a way to add/remove/list the ssrcs that can be removed by a stream. Opinions? Thoughs? -- Olivier Crête olivier.cr...@collabora.co.uk Collabora Ltd
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________ Farsight-devel mailing list Farsight-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/farsight-devel
