Re: [Openpbx-dev] AEL

[Beau Hargis]

AEL at least compiles into a dial plan. That last time I used res_perl, it 
leaked so much memory it crashed the system after an hour. res_js didnt seem to 
want to play well either. I remember it segfaulting. AGI is not an option in 
any way because the startup costs when a call comes in are too great. We have a 
machine that will get hit with 100 calls within 1 second.

The big issue is that Asterisk doesnt have any concept of asynchronous events 
being in control by a dialplan. Looks like OpenPBX still carries that baggage. 
IVRs and PBXs are by nature asynchronous. To do something in Perl, or any other 
language, I have to write wrappers and libraries to do things in such a way to 
make control the behavior of the system.  

Right now I have an app running on Asterisk that is done in AEL for the sole 
reason that anyone can look at it and see what it is doing and make quick 
changes. Because of my experiences with Asterisk we are considering Yate and 
Bayonne because they seem far more scalable and flexible.

In my opinion, OpenPBX needs a whole new concept of a dialplan not plugins for 
it. The way Asterisk does it is hideous and the implementation is horrible and 
unscalable.

-Original Message-
From: [EMAIL PROTECTED] on behalf of bkml
Sent: Mon 3/20/2006 11:48 PM
To: OpenPBX.org Developers Mailing List
Subject: Re: [Openpbx-dev] AEL
 

On Mar 21, 2006, at 4:10 PM, Beau Hargis wrote:

 I think we will have to port AEL or AEL2 to OpenPBX


P L E A S E ...

let's not open pandorra's box,

let's stay clear of AEL and focus on dialplan engine plug-ins instead.

res_js and res_perl are two such plug-ins already available and Tony  
said he was looking into making a res_io plugin, too. There are  
plenty of other languages to look at and evaluate first before  
considering AEL.

rgds
benjk









___ 
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail 
http://uk.messenger.yahoo.com
___
Openpbx-dev mailing list
Openpbx-dev@openpbx.org
http://lists.openpbx.org/mailman/listinfo/openpbx-dev


winmail.dat___
Openpbx-dev mailing list
Openpbx-dev@openpbx.org
http://lists.openpbx.org/mailman/listinfo/openpbx-dev

Re: [Openpbx-dev] AEL

[Beau Hargis]

On Wed, 2006-03-22 at 09:10 +1200, Daniel Swarbrick wrote:
 Nathan C. Smith wrote:
  
  Benjk and I were excited about the io language
  (http://www.iolanguage.com/about/).  It's very small, embeddable and
  extensible.
  
 
  From the website, Io is a small, prototype-based programming language.
 
 So is JavaScript. And far more widespread at this point in time.
 
 Please, please let's not go in search of a language that is 99% the same 
 as some other mainstream language, just to be different.

One of the questions that popped up over here about Io was regarding
library support. The benefits of something like python, perl and php is
that there is a huge library of modules to do just about anything you
want. I dont believe that JavaScript has such a huge library of modules,
either. 
___
Openpbx-dev mailing list
Openpbx-dev@openpbx.org
http://lists.openpbx.org/mailman/listinfo/openpbx-dev

Re: [Openpbx-dev] Read() dialplan app does not see m to behave as it should.

[Beau Hargis]

On Wednesday 21 February 2007 23:56, Mikael Bjerkeland wrote:


 Great, could you please make a patch with diff -Naur oldfile newfile 
 app_read.c.patch and attach it here? I'll make sure it is added. Thanks
 for your help!

I am going to hold off for a moment on that. The code is significantly 
different and the original opbx code and adds certain functionality that I 
need, actually. It allows, basically, the concatenation of multiple files to 
play while waiting for the defined event. I am going to experiment with a 
couple if things. I think I know what the problem may be after staring at it  
for a while.
___
Openpbx-dev mailing list
Openpbx-dev@openpbx.org
http://lists.openpbx.org/mailman/listinfo/openpbx-dev