(1) Full Mediation ========================== (a) Outgoing NODE_MESSAGE_LOCAL is wrapped in MEDIATED_MESSAGE_LOCAL (b) Mediated message sent will require and ACK and repeat if no ACK received. # of retries can be configured, but currently not per-variable. (c) Received MEDIATED_MESSAGE is unpacked as NODE_MESSAGE and handled, typically by uFldMessageHandler. (2) Partial Mediation ========================== (a) Outgoing NODE_MESSAGE_LOCAL is wrapped in MEDIATED_MEDIATED_LOCAL (b) If the message var is on the no_resend_var list, it is sent but no ACK message will be generated. Fire and forget. (c) Received MEDIATED_MESSAGE is unpacked as NODE_MESSAGE and handled, typically by uFldMessageHandler. (3) No Mediation ========================== (a) Outgoing NODE_MESSAGE_LOCAL is sent to other vehicle (b) Received NODE_MESSAGE is handled typically by uFldMessageHandler. Issue: When pMediator is being used, we normally shut off the the pSharing of NODE_MESSAGE_LOCAL to other vehicles. ALL outgoing NODE_MESSAGE_LOCAL publications are intercepted by pMediator and pShare shares this variable instead. We *could* modify pMediator to ignore certain NODE_MESSAGE_LOCAL publications, but then we would have to turn on sharing generally for NODE_MESSAGE_LOCAL. This would mean mediated messages would be transmitted twice. Once wrapped in MEDIATED_MESSAGE_LOCAL, and once as NODE_MESSAGE_LOCAL. If I understand you, you would like, for certain MOOS variables involved in a NODE_MESSAGE_LOCAL, to have pMediator ignore these messages, preferring instead that they just be sent with no mediation. My question is: For messages with partial mediation, they will not be repeated, and there will be no ACK message coming back. So there is only the overhead of adding a wrapper on send, and stripping the wrapper upon receipt. I don't think this is much overhead. The primary concern of not generating ACK or repeated messages has been achieved in partial mediation. Let me know what you think. Thx/Mike