Re^6: UDP server with IO::Socket::INET

Replies are listed 'Best First'.
Re^7: UDP server with IO::Socket::INET by rowdog (Curate) on Mar 05, 2010 at 12:54 UTC
No, I'm saying that it is possible to detect missing clients with ICMP but a much better alternative would be an existing ~~explicit connection~~ protocol, such as multicast. Update: I realized too late that multicast doesn't actually use explicit connections but that's part of the beauty of multicast.	[reply]
Re^8: UDP server with IO::Socket::INET by ikegami (Patriarch) on Mar 05, 2010 at 16:30 UTC
Ok, so your suggestion that multicast is an alternative to ICMP is wrong. You need some kind of connection and disconnection mechanism whether or not multicasting is used. Note that I don't think ICMP would even work as a disconnection mechanism. It will only tell you whether the machine is reachable (and might not even do that with firewalls), not if a UDP port is reachable. but that's part of the beauty of multicast. It's part of the beauty of UDP, as it is what allows multicast to exist.	[reply]
Re^9: UDP server with IO::Socket::INET by rowdog (Curate) on Mar 06, 2010 at 17:39 UTC
Ok, so your suggestion that multicast is an alternative to ICMP is wrong. You need some kind of connection and disconnection mechanism whether or not multicasting is used. What the fuck are you rambling on about now? Multicast explicitly does NOT require the server to know ANYTHING about the clients. You're just twisting my words to prove that you're smart and I'm dumb. Go away troll.	[reply]
Re^10: UDP server with IO::Socket::INET by ikegami (Patriarch) on Mar 06, 2010 at 21:02 UTC
Re^11: UDP server with IO::Socket::INET by Anonymous Monk on Mar 06, 2010 at 21:43 UTC
Some notes below your chosen depth have not been shown here
Re^11: UDP server with IO::Socket::INET by rowdog (Curate) on Mar 19, 2010 at 03:23 UTC