For inter-process comm on a single server, why not KISS and use message queues and POD structs?
On Mon, Aug 27, 2018 at 2:43 PM, Alan Carroll <solidwallofc...@oath.com.invalid> wrote: > Because most people probably dropped off the previous discussion on this > list, I want to call out that, as far as I can tell, the consensus for > upgrading the internal RPC mechanism is to use a JSON based message > exchange compliant with JSON-RPC 2.0 (https://www.jsonrpc.org/). We can use > YAMLCPP to parse messages and I think we can easily (externally) tweak > YAMLCPP to output JSON. This will be very interoperable with external tools > along with an easy way to pass relatively complex data between > traffic_manager / traffic_server and external tools like traffic_ctl in > both directions.
