[Telegraph-users] Adearsion/Telegraph cooperation instead of competition

[Jonathan Palley]

Hi Yitzhak -
   Jay and I discussed this a while ago.  At the time it was pretty  
clear that the use cases/syntaxes/DSLs were very separate.  Telegraph  
is designed for adding voice functionality to Rails application and  
the key design goal was to make it really tightly integrated into  
Rails.  Actually, Telegraph is an extraction from what we use at my  
company and has suited as well for doing all the voice functionality  
on top of the very large Rails system we run.
I can't speak for the Adhearsion team but it certainly seems that the  
goals and ideal use cases of Adhearsion are for making a framework  
for building voice applications independent from the web.  From an  
architectural and design standpoint there is a large difference.

Having said that, there is a large duplication that I would like to  
see remedied: the core AMI/AGI interface libraries can certainly be  
shared.  I think this would be a good thing.  For instance, I noticed  
that Adhearsion has listed as one of their TODO's that the AMI module  
needs a rewrite.  I've offered this before (not sure why it wasn't  
picked up), but the AMI module we've been using in Telegraph is ugly  
but very stable.  We've been running it basically nonstop for a year  
now and the only problem was a memory leak we fixed a few months  
ago.  I believe this is a good example: the AMI stuff Asterisk sends  
back is messy enough that there is no reason to have multiple  
libraries doing the same thing.

Having said that, we are working on refactoring it and the AGI stuff  
again to using EventMachine as we can achieve much higher throughput/ 
lower CPU usage and cleaner code this way.  We are also abstracting  
out so we can drop FreeSWITCH support in.  We'll release it when we  
have a chance to clean it up and get it out.  Again, turning this  
libraries into a shared library would certainly be ideal and I would  
encourage it.

My main prerogative is of course writing stable and effective code/ 
DSL's that suit my companies Rails based system (which is a complex  
distributed call center/oral language learning/international calling  
system).  If someone can champion and shepherd a proper extraction of  
these core libraries we will certainly contribute and run it with  
Telegraph on our main systems.  I would love to see it happen.

Thanks for starting the discussion.

Jonathan
On Dec 14, 2007, at 6:02 PM, Yitzhak Bar Geva wrote:

> Wondered whether we're not going to end up with a duplication of  
> effort between Telegraph and Adhearsion whereas cooperation between  
> Adhearsion and Telegraph as a single project could result in an  
> immensely improved framework. What benefit does two seperate  
> projects bring while we could be concentrating the efforts to a  
> better end in the context of a single project?
> Feedback from the user community is warmly welcomed
> _______________________________________________
> Telegraph-users mailing list
> Telegraph-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/telegraph-users