hhaim
commented
3 years ago @jsmoon good question. When I change the design of zmq_async SUB/PUB issue I wanted to remove this channel completely and keep only the REQ/RES. You are right in general that there is no need for trex-global and trex-barrier as the client designed was changed long ago to use only REQ/RES due to scale issues of pgid (even the GUI). The reason to keep this channel (not the messages) is to get the interrupt of an events and then read it in REQ/RES this keep the regression fast and by that it does not require a massive change in clients (e.g. GUI ).
Back to your question, I think it is possible to remove those messages with the new design.
@hhaim, I have found a mismatching between T-Rex client and server for the async message handling. According to my analysis, the server publishes "trex-global", "trex-barrier" and "trex-event". But, the client handles the "trex-event" only because it handle the messages gotten by the "get_async_events".
If you did not intend to ignore the "trex-global" and "trex-barrier" messages, the client needs to handle them properly.
If you did intend this behavior, I think you'd better remove publishing the "trex-global" and "trex-barrier" messages.