On 12 Mar 2014, at 21:51, Daniel-Constantin Mierla <[email protected]> wrote:
> evapi: new module to push event details via tcp to external applications I think this is a great start - but also (based on my exprience with Asterisk manager) complex. Would it be beneficial to have a larger discussion about requirements and formats before too much code is produced? If I understand correctly, we only have one type of message - "event". Is there a need for other types of messages? Using a Json payload for the payload seems clever and extensible to me. When a connection is opened, should we send an event to identify a particular server, version of the server and version of the evapi so that client can handle changes and upgrades in the future? Should potential commands from client to server be done over the standard RPC commands - do we really need a new way for clients to control Kamailio? The event part was clearly missing, but we have a few ways to connect to Kamailio already. Can we protect this listen port with TLS? Do we need authentication? Just a few thoughts. This will be a very important new feature, so it's important we get it right. Thank you for starting this, Daniel! /O _______________________________________________ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
