Hi Eloy, I added the framework for tagging connections to simplify the development of further extensions via sending a structure packaged at once.

I haven't extended the config functions for evapi relay, because I thought we may need to decide on naming.

We can add a second parameter for the tags in evapi_*relay() or we can add a new pair of functions: evapi_relay_multicast(data, tag), plus the one for async.

Then, if you want to filter by ip:port, then evapi_relay_unicast(data, ip, port) can be added. Even when sticking to tags only, could make sense to have evapi_relay_unicast(data, tag) which stops after matching first tag. The multicast is walking to all connections to see if the tag matches.

This unicast/multicast can be a new field in evapi_msg_t as an integer, so it won't need any speciall allocation to pass to evapi workers.

What do you think?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub