3 ms·
I remember browsing the directories of a Broadsoft Broadworks application and network servers back in the early 2000s and being shocked at just how much of the
by mrkstu 8y ago
I remember browsing the directories of a Broadsoft Broadworks application and network servers back in the early 2000s and being shocked at just how much of the product was implemented in Perl. Many fortunes have been made on the back of interpreted code.
- snuxoll 8y agoThere's not much in the SIP protocol itself (I'm not talking the RTP streams here, just SIP) that can't be handled with adequate performance in higher level languages (whether interpreted or not). At the end of the day it's a bunch of XML over TCP sockets, a lot of your function/method calls are going to be into libc (networking), something like sax (xml), and likely database access (libpq/whatever), the coordination of these with perl is going to cost you some CPU time but likely not enough to justify the extra expensive (man hours) doing it in C or something similar. The RTP streams, that you may want to handle in a lower level language since you're talking soft real time being a must.
- JdeBP 8y agoUDP sockets, not TCP ones. And don't forget about the bunch of MIME and Internet Message format that precedes the XML. (-:
- moises_silva 8y agoSIP works over a variety of transports, both TCP and UDP are used. You can tell UDP is certainly more common but any RFC-compliant stack is supposed to support both because large UDP packets (> MTU) are supposed to be sent using TCP. The bulk of the protocol doesn't require XML at all actually, it's the SIP SIMPLE and presence extensions that do. But for the core SIP spec and your run of the mill VoIP call setup, no XML is needed.
- JdeBP 8y agoApparently I was being too subtle with the gentle reminder not to forget the MIME and Internet Message stuff.