Hello, First of all, I upgraded callweaver-perl using asterisk-perl 0.10 (it was based on 0.09). I'd appreciate some feedback on this (ticket #343).
Now I'm working on a partial rewrite of CallWeaver::OGI - using CPAN modules and automethods, I've cut the code size by 50%, improved its readability and grown the documentation to 200% for good balance :-) I've still got to write a real testsuite and I'll be ready to send a patch. However, I'm wondering if this is really the best course of action. This will definitively fork the Asterisk::AGI module, and without contacting the original author first I'm not sure it is even needed. Indeed, as far as I can tell the only difference between Asterisk::AGI and CallWeaver::OGI is the prefix used to pass variables around (agi_$name: $value vs. ogi_$name: $value). This could easily be configured at runtime rather than through a complete fork. Has someone tried to contact James Golovich about it? Should I? While waiting for your answers I'll get that testsuite done - my work would fit just as well in a unified Asterisk::AGI than in CallWeaver::OGI. -Waba.
signature.asc
Description: Digital signature
_______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
