I don't know if the reason to this issue happens is the project is now still under development stage. but through observing the source code, I found that maybe one of the reason is the dartzmq doesn't provide the receive function, and the inner strategy is using loop to handle the receive data without sending data for reply. but whether I use reply mode or request mode, zmq doesn't allow no sending action within two receiving actions. so, it seemed the exception occurs. i want to know why the dartzmq has not provide receive funciton directly? or the dartzmq developer has had a solution to solove the problem? I am looking forward to the reply very eagerly. Thanks in advance.
I don't know if the reason to this issue happens is the project is now still under development stage. but through observing the source code, I found that maybe one of the reason is the dartzmq doesn't provide the receive function, and the inner strategy is using loop to handle the receive data without sending data for reply. but whether I use reply mode or request mode, zmq doesn't allow no sending action within two receiving actions. so, it seemed the exception occurs. i want to know why the dartzmq has not provide receive funciton directly? or the dartzmq developer has had a solution to solove the problem? I am looking forward to the reply very eagerly. Thanks in advance.