Juha,
Thanks for the comment.
I don't disagree with anything you've said. The decision on UDP was based on the fact that we're looking at a massive deployment on a VPN so TLS never needed to be addressed.
NOTE: Massive = n > 500000+ subscribers
Add to this the fact that it would be clunky to call t_replicate() for a potentially varying number of sip proxies and we came to the conclusion that a multicast version of t_replicate() will do the trick for replicating REGISTER messages to all the sip proxies on the VPN.
Thus we arrived at the UDP decision. If there are better ways to achieve 99.999% uptime while having independent ser, serweb, and sems farms the please share. I'd love to validate our work or shoot holes in it before it goes primetime.
Cheers, Paul
--- Juha Heinanen jh@tutpro.com wrote:
Java Rockx said:
Also, we are very close to publishing a patch for using UDP sockets
rather than
the FIFO or Unix Sockets.
why unreliable udp instead of reliable tcp? if the system is distributed to possibly far away hosts, tcp would seem a much better choice. also, tcp would support tls.
-- juha
__________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail