The same node cannot subscribe to messages published by itself about ecal HOT 3 CLOSED

Hi @jiejieTop,
yes it can subscribe to traffic from the same node, but you have to enable it explicitly (I don't remember why exactly, probably to reduce load..)

  // enable loop back communication in the same thread
  eCAL::Util::EnableLoopback(true);

This function needs to be called after eCAL::Initialize() and you can communicate inside the same process.

from ecal.

Hi @jiejieTop, yes it can subscribe to traffic from the same node, but you have to enable it explicitly (I don't remember why exactly, probably to reduce load..)

  // enable loop back communication in the same thread
  eCAL::Util::EnableLoopback(true);

This function needs to be called after eCAL::Initialize() and you can communicate inside the same process.

Thanks a lot, this works, but why need to explicitly enable？

from ecal.

Yes, it's following the same logic like socket communication. Normally you don't want to read your own content. We had scenarios in the past were user used the same topics for incoming and outgoing interfaces in different nodes and expected to get triggered by external publishers only.
Btw. there is another transport layer called INPROC that is default switched off. That one can be used to just call the subscribers callback by the publishers send method. But that layer has some other drawbacks (hard coupling publishers and subscriber single threaded) that finally often decrease overall performance.

from ecal.