Vinod Parameswaran wrote: > Hi Marius, > > Thanks. I am not sure I quite understood what you mentioned in your previous > mail. > Do you mean use a customized stack at the transport layer in order to make > multiple connections? > In that case, I am afraid I do not understand why I need to tweak the layers > above? > > The point is that I am not sure whether making those customizations would be > a straightforward task. I was using PJSIP previously, and those libraries are > strictly single-threaded, afaik. That is you cannot do any customization at > any layer to achieve multi-threading. > > Hope I have read your mail correctly. If not, kindly clarify. > > best > Vin > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > Hello again,
Because I replied personally (i don't think application design are relevant to sip-implementors), I am first making a note saying that I suggested dropping MT and using a IO Multiplexing technique. This is possible in PJSIP adding new Transports for each network, and also in Sofia. About MT, check this documentation about locking and thread support in Sofia http://sofia-sip.sourceforge.net/refdocs/su/group__su__wait.html . After a quick read it seems that Sofia is using poll() for IO multiplexing and probably several threads for message handling (parsing, transaction and ua). Hope this helps. Marius _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
