To make things simple, we'll currently assume that only a single flowgraph exists (I'm keeping in mind multiple flowgraphs, but not implementing it that way, just not making it harder to implement that).
To the derived CpMediaInterface class that we'll use (something like CpTopologyGraphInterface) we'll add a method to fetch a flowgraph queue. The application could then call the static operation from a typed resource, passing the flowgraph queue, a resource, and any parameters necessary for the operation. Abstracting out to posting to other queues is out - as more information, and crossing of library boundaries occur if you do something like that. Here's an example: 1. Application has mediaInterface, requests a flowgraph from the mediaInterface 2. Application then calls MpMixer::setWeight(flowgraphQueue, resourceID, weightIndex, weight) 3. static setWeight constructs setWeight message, posts to flowgraphQueue 4. Message then gets processed like anything else in the queue. -- Keith Kyzivat SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
