Developing nodes: How to avoid or detect emitted client messages bouncing back?

I think I asked this question before but still have no definite solution.

Problem: A client emits a message. This will be transmitted to all connected clients including the emitter. In some cases it is useful to detect that an incoming message is actually the own message (and forget this one)

Question: how to do that without a workaround like comparing with the own state (which could already be outdated because the user handling a slider for example)

The client could compare the socketid but how can the client get its own socktetid to compare with?

To check the pure existence of msg.socketid don’t help because a message can allways carry a socketid properly (i.e. originating from another widget)

Any hint appreciated.:grinning:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.