The way we do this is send a special message saying that a broadcast will be sent next. Brian
probe() checks only for messages sent by send(), not by broadcast(). Matthias
Thanks, I spend most of my time broadcasting, and sometimes sending.... I guess that means in the slave processes: . use mpi::broadcast() . if the received value is a signal that a send() to me will be issued next, then I'll recv() About the broadcast() function, I obviously have many types of messages to send, would you rather: 1. send a broadcast with just an int (like a tag) to tell which broadcast is following next or 2. construct a virtual base class my_mpi_broadcast , derive all the sendable broadcasts from it, from sender, send actual instance of derived from my_mpi_broadcast, and at receiver, can the mechanism reconstruct for me the derived class? (with boost::serialization) Is 2 doable at all? If so, pros/cons regards,