[Freeswitch-users] best FS interface for development

[Christopher Rienzo]

For arbitrarily large and complex systems, I'd keep FreeSWITCH as dumb as
possible so that you can easily cluster them.  So, modules that allow
external control (mod_event_socket, mod_erlang_event, mod_httapi,
mod_xml_curl) are all good choices.

Event socket is pretty popular; Plivo and Adhearsion both use it.  The
2600hz guys use mod_erlang_event.  And I've heard of plenty of people that
use mod_xml_curl.

Chris



On Fri, Sep 7, 2012 at 9:43 AM, Brett Clark - Grasshopper <
bclark at grasshopper.com> wrote:

> There seems to be at least 4 general ways for customizing FS:****
>
> - Use the event socket and build an app to interface with it****
>
> - Use mod lua, or similar, to develop in a particular language****
>
> - Develop your own ‘module’ to interface directly with the core****
>
> - Use the XML interface to implement IVR, PBX, and voicemail type
> functionality and all the rest.****
>
> ** **
>
> How prevalent is each approach in the community?  It seems like everyone
> is doing a little of both, but maybe someone has a better handle of what
> the actual ratios are?  ****
>
> ** **
>
> Which is best suited for an arbitrarily large and complex application?  I
> realize this isn’t a simple question—what I want is to understand the most
> evolved and featureful way to interface with FS?  I don’t want to adopt an
> approach which isn’t being actively maintained or is missing features.  As
> new stuff is added to FS, which approach will allow me to adopt those new
> features most easily?****
>
> ** **
>
> Thanks!
> Brett****
>
> ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20120907/c162477e/attachment.html