Hi, Arnaud Loonstra <[email protected]> writes:
> The other way to analyse the problem is to check how EVASIVE is used at > the moment... and maybe if it used at all. My experience is that since > its introduction in a stable version, not once was is useful in > real-world cases for me.` Initially I thought EVASIVE was some magic way to determine that the overall application was "misbehaving" (hung/looping). After the obvious realization that the Zyre node has no general way to determine what is going on in other threads it was not clear what the point of EVASIVE was. I hadn't thought about having a peer follow up with a PING but that also only tests that the Zyre actor is alive. I still hope to find some kind of dead-man switch and would like it to be done through Zyre since it's ENTER/EXIT are so related. Ideally, we might add a new API message, eg "ALIVE", which only serves to reset the evasive timeout. My application could do some Zyre chatting just for the side-effect of refreshing the evasive timeout. But, I don't have any need for the resulting chat messages. Maybe I can have the Zyre node WHISPER to itself? -Brett.
signature.asc
Description: PGP signature
_______________________________________________ zeromq-dev mailing list [email protected] https://lists.zeromq.org/mailman/listinfo/zeromq-dev
