On Thu, Nov 8, 2012 at 10:24 AM, Matthew Jordan <span dir="ltr"><<a href="mailto:mjordan@digium.com" target="_blank">mjordan@digium.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 11/08/2012 07:35 AM, joachim wrote:<br>
><br>
> I can't speak for the other projects due to a lack of experience with<br>
> them, but we (Zoiper) are very happy with Resiprocate. The product is<br>
> rock stable and the core team is very skilled.<br>
><br>
<br>
</div>Given that reSIProcate is written in C++, it would be fairly difficult<br>
to adopt for the Asterisk project. Not impossible, but it would most<br>
likely entail having to write wrappers around the C++ objects ourselves<br>
that expose them in a manner consumable by C applications. This means<br>
that we would either have to have a C++ wrapper module in Asterisk<br>
(eek), or else we would have to have a C++ library that wraps<br>
reSIProcate and have a resource module consume that intermediary<br>
library. Note that this would also eliminate some of the benefit of<br>
having reSIProcate as a packaged library.<br>
<br>
While certainly worth looking at, it would be a significant amount of<br>
work just getting that SIP stack incorporated in a usable fashion in<br>
Asterisk.<br></blockquote><div><br></div><div>I'm not sure that I understand the technical limitations here. It's certainly possible write an Asterisk module in C++ today and consume all of Asterisk's C APIs. There have been C++ modules in the past.</div>
<div><br></div><div>If there's a concern about having a critical module in C++ in a community otherwise working in C, and the potential skill gaps resulting in bad code ... I get that. It's certainly worth taking into account.</div>
<div><br></div><div>-- </div><div>Russell Bryant</div></div></div>