On 1/11/22 18:01, Duzan, Gary D via tipc-discussion wrote:
>     Is there a reliable way for a process to determine if a TIPC socket 
> address points to an open socket without disturbing the target process? I'm 
> hoping to be able to determine the liveness/reachability of a datagram peer, 
> at least roughly, without taking on the complexity of additional messaging 
> (or group membership and join/leave tracking).
>
>     Thanks.
It depends on the socket type and state. If it is a connected socket
there is a built-in mechanism that will make sure that the peer socket
is immediately notified, and the user will receive this notification.
The same is the case with group sockets.
For DGRAM sockets there is no such mechanism, since it is impossible for
TIPC to know which peers need to be supervised.

///jon

   Thanks, Jon. I'm dipping my toes in the group communication waters, and so 
far it looks like I will be able to use it.

Gary Duzan
FIS GT.M Core Team

________________________________
From: Jon Maloy <jma...@redhat.com>
Sent: Wednesday, January 12, 2022 11:37 AM
To: tipc-discussion@lists.sourceforge.net 
<tipc-discussion@lists.sourceforge.net>
Subject: EXTERNAL: Re: [tipc-discussion] TIPC Socket Liveness Check

CAUTION: This email originated from outside of the company. Do not click links 
or open attachments unless you recognize the sender and know the content is 
safe.



On 1/11/22 18:01, Duzan, Gary D via tipc-discussion wrote:
>     Is there a reliable way for a process to determine if a TIPC socket 
> address points to an open socket without disturbing the target process? I'm 
> hoping to be able to determine the liveness/reachability of a datagram peer, 
> at least roughly, without taking on the complexity of additional messaging 
> (or group membership and join/leave tracking).
>
>     Thanks.
It depends on the socket type and state. If it is a connected socket
there is a built-in mechanism that will make sure that the peer socket
is immediately notified, and the user will receive this notification.
The same is the case with group sockets.
For DGRAM sockets there is no such mechanism, since it is impossible for
TIPC to know which peers need to be supervised.

///jon

>
> Gary Duzan
> FIS GT.M Core Team
>
> The information contained in this message is proprietary and/or confidential. 
> If you are not the intended recipient, please: (i) delete the message and all 
> copies; (ii) do not disclose, distribute or use the message in any manner; 
> and (iii) notify the sender immediately. In addition, please be aware that 
> any message addressed to our domain is subject to archiving and review by 
> persons other than the intended recipient. Thank you.
>
> _______________________________________________
> tipc-discussion mailing list
> tipc-discussion@lists.sourceforge.net
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Ftipc-discussion&amp;data=04%7C01%7Cgary.duzan%40fisglobal.com%7Cc5807cf1a5404ced672608d9d5e9689b%7Ce3ff91d834c84b15a0b418910a6ac575%7C0%7C0%7C637776020722484859%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=wXXdGz4V0iGHSXNiljgBu9BW8HjbYr80SuXjA3g1iK8%3D&amp;reserved=0
>



_______________________________________________
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Ftipc-discussion&amp;data=04%7C01%7Cgary.duzan%40fisglobal.com%7Cc5807cf1a5404ced672608d9d5e9689b%7Ce3ff91d834c84b15a0b418910a6ac575%7C0%7C0%7C637776020722484859%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=wXXdGz4V0iGHSXNiljgBu9BW8HjbYr80SuXjA3g1iK8%3D&amp;reserved=0
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.

_______________________________________________
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

Reply via email to