On 2024-09-16 07:58, prakash bisht wrote:
Hi Hi Tung,Xin,John,
We are using tipc multicast sockets for publisher/subscriber type of
application.
Below are the socket details
socket type : SOCK_RDM
tipc addr type : TIPC_MCAST
We would like to know if the successful bind() call on the subscriber
socket guarantees that the subscriber is ready and no publication
would be missed ? Or shall we wait for some time before assuming the
subscriber socket is ready ?
There may be (very) a small lag between the return of the bind() call
until the bind is registered on all the other nodes.
The proper way to get around this is to let your "publishers" use the
TIPC subscription mechanism to keep track of your
"subscriber", i.e., they don´t start publishing until they have received
a notification that the subscriber is bound
to the service address/range.
///jon
Thanks and Regards,
Prakash
_______________________________________________
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion