[asterisk-dev] AstriDevCon - PineMango

Brian Degenhardt bmd at digium.com
Thu Oct 9 14:19:24 CDT 2008

BJ Weschke wrote:
> Brian Degenhardt wrote:
>> http://www.simionovich.com/wp-content/uploads/2008/10/image2_diagram1.jpg
>> Ok, now that we've designed the perfect API (wasn't that easy?), how
>> does one use it?  One of the things we floated is perhaps a pluggable
>> inteface to res_api that deals with connections and encoding.  Me
>> personally, I'm sorta partial to a socket that uses a binary data
>> encoding method like ASN.1 or Google Protocol Buffers.  But why not have
>> another interface that does XML over XMPP?  Shared memory is another
>> idea which may provide a lot of speed.  Hell, for the masochists we
>> could do a textual socket interface that's encoded like manager
>> (although we'd have to figure out how to do deep hierarchical data).
>> This pluggable-transport idea may be too ambitious, but it's something
>> to consider.
> I give a big +1 to the pluggable transport idea, and that's one of
> those things where if it isn't done from the start, I don't really
> believe that it every will be because the task to migrate will be too great.

Even if we can't do it in res_api, we'll still have all the little blue
boxes down below, and you can always go write your own tan/olive
component that transports the internals however you want.


More information about the asterisk-dev mailing list