<DIV>
<DIV>The first wheel was said to be a log, then probably 2 logs </DIV>
<DIV>today it is rubber , metal , wooden etc. </DIV>
<DIV> </DIV>
<DIV>J.K. I'm sure debate over reinventing the wheel or if perl sucks or not </DIV>
<DIV>will see more airtime than the topic of using perl in asterisk being cool or not will.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Everything I needed in the app_perl was located right in pbx.c from aterisk</DIV>
<DIV>so I actually include that c file into mine out of fear of losing compatibility </DIV>
<DIV>since it evolves so fast. What I do now is by includeing pbx.c I can </DIV>
<DIV>call any of the important func that asterisk itself uses so I re-implement </DIV>
<DIV>my own mini-command interepter for the return value of a perl fucntion</DIV>
<DIV>to send to me then I parse those commands and feed them to real asterisk calls.</DIV>
<DIV> </DIV>
<DIV>So for a start all the func i frontend in app_perl could be perlified with xs</DIV>
<DIV>and buried in the module as a package so the per func could use it and call those </DIV>
<DIV>functions. </DIV>
<DIV> </DIV>
<DIV>So you get C embedding perl embedding C to call func from the original C </DIV>
<DIV> </DIV>
<DIV>Sounds Silly but you could avoid inventing large painful wheels in C</DIV>
<DIV>by hooking up perl and its army of premade wheels (I made < 1k webserver </DIV>
<DIV>func to load in asterisk already)</DIV>
<DIV> </DIV>
<DIV>Lot's of possibilities........ perl likes to parse text more than anything else </DIV>
<DIV>you could develop the config file parsing engine that way and go to </DIV>
<DIV>town making up a format rather than dealing with coding the parsing </DIV>
<DIV>and you can teach asterisk to read config files from different systems etc. </DIV>
<DIV>maybe asterisk is the emacs of pbx systems (oh oh here come more flames going off on a tangent) YES I like PERL! and EMACS!</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>On Monday, Jun 23, 2003, at 10:34 America/Los_Angeles, James Golovich <BR>wrote:<BR><BR>> No point in reinventing the wheel here. PersistentPerl (aka <BR>SpeedyCGI)<BR>> can eliminate the startup cost for using perl with AGIs.<BR>><BR>> It works great, and even allows the processes to reuse database<BR>> connections<BR><BR>Speed is not the only reason to embed Perl in the "host application".<BR><BR>The real cool stuff comes if the API of the host application is exposed <BR>to Perl, so you can write asterisk modules in Perl (like you can use <BR>the Apache API from Perl with mod_perl).<BR><BR> - ask<BR><BR>-- <BR><A href="http://www.askbjoernhansen.com/" target=_blank>http://www.askbjoernhansen.com/</A><BR></DIV>
<DIV> </DIV>
<DIV> </DIV></DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/">SBC Yahoo! DSL</a> - Now only $29.95 per month!