posted on Tuesday, April 27, 2010 - 02:16 pm
When a new participant comes up does it send a broadcast message to others announcing its presence?If so,does it also provide some unique key/id to identify itself among other nodes?and who decides the ID? I believe,the pub and sub ids would be stored in each of the participants .When a resend of old data happens would it be multicast or sent to the late subscriber only?
in OpenSplice DDS, DDS entities get assigned unique ID's and the built-in topics capture those. W.r.t. re-sending of 'old' data (assuming you mean interest in non-volatile i.e. TRANSIENT or PERSISTENT data) the related data-transfers depend on the fact if there was already an 'aligned' OpenSplice durability-service running on the node where the late-joiner is started, if so, then the data is already present (in shared-memory) so availability is 'instantaneous' and if not (i.e. a complete node-restart or a durability service that works 'on-request' i.e. one where alignment is triggered by the emergence of a local subscriber), the data will be provided by a remote node (doesn't need to be the publishing node 'per se')