<div class="gmail_quote">On Wed, Apr 21, 2010 at 9:52 AM, Timothy Rodriguez <span dir="ltr"><<a href="mailto:timothy.rodriguez@gmail.com">timothy.rodriguez@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It would significantly complicate the architecture to bring in java<br>
for developing channel types. I think lua would be a better language<br>
for extensibility. However, I think java would've worked had asterisk<br>
been implemented entirely in it, but a functional language like erlang<br>
might've lent itself better to the type of concurrency asterisk<br>
requires. Btw, erlang is a vm language as well, so it has similar<br>
properties to the jvm, but is used by a telco for implementing pbxs.<br>
Still, much less people know erlang than java or c.<br>
<br>
</blockquote></div><br>I don't understand why you're saying that. I already mentioned the jasterisk project. I don't know if they let you do channel drivers or not, but I don't see any technical reason why you could not. It's just a matter of writing the right bindings. Lots of open source projects have java bindings implemented as external projects. There's the jirr project (<a href="http://sourceforge.net/projects/jirr/">http://sourceforge.net/projects/jirr/</a>) for example that lets you use irrlicht from java.<br>
<br>I wouldn't expect an explosion of channel drivers just because you could write one in java. If there was that much interest in java there would already be bindings to write channel drivers and people already doing it.<br>