|
|
|
|
|
|
by tsimionescu
2069 days ago
|
|
|
This leaves higher application code to handle duplicated messages. It also does not handle cases where the client connects later than the server send, but would still like to receive the server messages. It also doesn't handle rate control (overwhelming the network). These may all be fine for your application, and then 0mq is an excellent fit. But I think that for most applications, having some kind of pre-implemebted solution to all of these problems, even with slightly more overhead, is extremely valuable. |
|
|
True, better send twice than never.
> the client connects later than the server send
Server only responds, never sends anything.
> overwhelming the network
"broker" is handling it nicely
I strongly agree that zmq will not fit in every use case. Always search for best option.