<p>License is less important in a socket interface lib.<br>
Its not really a big deal what license it is guys.<br>
However, I did create a BSD ESL lib distributed with FS to make sure nobody would have any license problems connecting to our stuff.<br>
If you don't like this lib consider using swig on the wrapper lib in libesl like I have done for perl, lua, php, python, ruby etc.<br>
</p>
<p><blockquote type="cite">On Jun 20, 2009 12:15 PM, "paul.degt" <<a href="mailto:paul.degt@gmail.com">paul.degt@gmail.com</a>> wrote:<br><br>Not unless you combining GPL and MPL code in one binary, which I find<br>
highly improbable in case of FreeSwitch.<br>
And even in this case there seems to be a workaround:<br>
<br>
"However, MPL 1.1 has a provision (section 13) that allows a program (or<br>
parts of it) to offer a choice of another license as well.<br>
If part of a program allows the GNU GPL as an alternate choice, or any<br>
other GPL-compatible license as an alternate choice,<br>
that part of the program has a GPL-compatible license."<br>
<br>
<a href="http://www.fsf.org/licensing/licenses/index_html#GPLIncompatibleLicenses" target="_blank">http://www.fsf.org/licensing/licenses/index_html#GPLIncompatibleLicenses</a><br>
<p><font color="#500050">
Brian West wrote:
> There actually are issues between the GPL and MPL :P
>
> /b
>
> On Jun 20, 200...</font></p></blockquote></p>