Hi, I'm starting a SIP stack. For now it creates a new thread for processing each request/response received via TCP/UDP.
But now I'm learning about Reactor Pattern [1] that doesn't use threads for each request but an event based model. Due to the complexity of SIP transport and transaction layer, I wonder if Reactor Pattern is appropiate for SIP. For example, in SIP the TCP connection should remain open after a transaction, a dialog can involve several transactions each one using a different transport connection (mobility?, network failover?), replies are not always sent using the incomig request connection, a single TCP connection can contain various totally independent requests... Well, I'm a complete newbie in those subjets, can any SIP developer explain me if Reactor Pattern could be feasible and useful for a SIP stack? Thanks a lot. [1] Reactor Pattern: http://en.wikipedia.org/wiki/Reactor_pattern -- Iñaki Baz Castillo _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
