[asterisk-dev] Locking, coding guidelines addition

Russell Bryant russell at digium.com
Thu Jul 3 22:05:15 CDT 2008

----- "Grey Man" <greymanvoip at gmail.com> wrote:

> You could always move the signalling into managed code (.Net, Java
> etc.) and make use of an existing tried and true reference counting
> and memory management infrastructure. The RTP/audio processing would
> have to stay in the C runtime to keep the ~1ms timing granularity.
> I know this will go down like a lead balloon but thought I'd mention
> it anyway. It is worth noting that some operating systems components
> are now being written in managed code so if it's performant enough
> there it would be performant enough for signalling in Asterisk. Not
> to mention saving re-inventing the wheel.

I don't want to start a language war, but we do find ourselves reinventing
a lot of things that are provided for you in C++.  However, converting the
code base to C++ is not really feasible or worthwhile.

Russell Bryant
Senior Software Engineer
Open Source Team Lead
Digium, Inc.

More information about the asterisk-dev mailing list