Juha Heinanen wrote:
Dan Pascu writes:
> IMO, OpenSER's architecture is well suited for UDP clients and at most
> some TCP/TLS peers. But even in this case if a peer is down and there are
> many connection towards that peer, again many TCP workers will be
> blocked, and other TCP peers cannot be handled meanwhile.
dan,
how does this differ from the case where UDP UAS is down and does not
respond and openser tm module keep re-sending the request until timeout
occurs?
I guess the UDP retransmissions are not sent by the worker threads, but
by a timer thread? And UDP sending is non-blocking.
With TCP, if a new connection is needed, the TCP connection will be set
up by the worker thread. Thus, a new TCP connection can block all
workers (just as a TLS handshake or DNS lookup)
Please correct me if I'm wrong.
regards
klaus
-- juha
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
--
Klaus Darilion
nic.at
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
