Hello, On 3/21/07, Keith Kyzivat <[EMAIL PROTECTED]> wrote: > What we propose to do is to put the messaging methods as static methods on > the specific resources that know about the message. Each of these static > methods would take as parameters the OsMsgQ& queue to add the message to, a > UtlString& resource name indicating the resource that this message is to be > ultimately received and processed by, and any arguments that the operation > needs to take. > For example: > > MprBridge::setMatrix(OsMsgQ&, UtlString& bridgeName, int mixVectorLength, > int mixVectorWeights[], ...) > > The reason for a queue as a parameter is that one may wish to send the > message to the resource to the flowgraph, to the resource itself, or to the > MpMediaInterface (specifying a flowgraph - since there's the possibility > that the interface can contain more than one flowgraph).
I do not understand this design well, so I'll here is my questions: Who is the owner of message queue, passed to this methods? I.e. who create and delete it and who sink and process messagesfrom it? Am I correct that flowgraph and MpMediaInterface have their own queues and they pass their own queue to this static methods, while resources do not have one and could not be accessed only via pointer. How flowgraph will bw selected when posting message to MpMediaInterface? -- Regards, Alexander Chemeris. 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/
