[sr-dev] [kamailio/kamailio] evapi: Added destination address on evapi_relay (#596)

[Daniel-Constantin Mierla]

If you get the IP:PORT in event route, then you can also set the tag there and can be inside the evapi connection structure, no need for htable anymore. You need to keep the relation of the IP:PORT and service somewhere, same can be done also with the tag name and service.

The benefit is that the tagging allows two or more connections to be tagged with same name and then send the message to all of these ones. Practically, more granularity, allowing to send to one, many and all. Also, at some point one may want to add transport as a constraint there, not only the address and port.

You indented now everything there, apparently there was other code not indented with tags, but now the patch looks bigger.

For the new structure, the data field can be str, not pointer to it, because it is all in memory. Also, all should be allocated at once, like it was before, making easier to deallocate and simplify the code in the evapi side.

Anyhow, I will add the support for tagging and get the framework with a data structure, you can then add support for ip:port if you need specific this case --  I am fine with that.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/596#issuecomment-217374772
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20160506/834fe471/attachment.html>