On quinta-feira, 29 de setembro de 2016 06:11:11 PDT Jaewook Jung wrote: > As you know, if you send any multicast message with IP connectivity, it is > delivered to you too, which means you can find your own resources by > findResource on both(server/client) mode. > > I think it seems not right. > There is not any usage scenario to send a message to itself by network > communication. If someone do this way, it makes unnecessary cost though > this can be done locally. And most of all, it breaks a consistency on > functionality since all other adapter except IP cannot send to itself.
Right. IoTivity should ignore its looped back queries. > So I suggest to filter all message sent by itself on IP connectivity. > > There is a socket option(=IP_MULTICAST_LOOP) to block the multicast loop > back, but it makes even all the other process cannot receive a message. So > it could be possible to filter using 'ip+port' for each process even on > same host. That sounds like the correct approach. When receiving a datagram whose source matches the process's own IP and port numbers, simply drop it without processing. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
