Skip to content
Browse files

Merge pull request #309 from jbohren-forks/master

Chapter 8 Typo: broadcast should be multicast
  • Loading branch information...
2 parents d727c6e + 4b6dbcd commit c9a2f8be634dc71f2d617799070cafe437909eb4 @hintjens hintjens committed Mar 23, 2013
Showing with 1 addition and 1 deletion.
  1. +1 −1 chapter8.txt
View
2 chapter8.txt
@@ -339,7 +339,7 @@ However, sadly, there's a fatal flaw in my idea of using {{ICMP_ECHO}} to discov
+++ Cooperative Discovery Using UDP Broadcasts
-Multicast tends to be seen as more modern and "better" than broadcast. In IPv6, broadcast doesn't work at all: you must always use broadcast. Nonetheless, all IPv4 local network discovery protocols end up using UDP broadcast anyhow. The reasons: broadcast and multicast end up working much the same, except broadcast is simpler and less risky. Multicast is seen by network admins as kind of dangerous, as it can leak over network segments.
+Multicast tends to be seen as more modern and "better" than broadcast. In IPv6, broadcast doesn't work at all: you must always use multicast. Nonetheless, all IPv4 local network discovery protocols end up using UDP broadcast anyhow. The reasons: broadcast and multicast end up working much the same, except broadcast is simpler and less risky. Multicast is seen by network admins as kind of dangerous, as it can leak over network segments.
If you've never used UDP, you'll discover it's quite a nice protocol. In some ways, it reminds us of 0MQ, sending whole messages to peers using a two different patterns: one-to-one, and one-to-many. The main problems with UDP are that (a) the POSIX socket API was designed for universal flexibility, not simplicity, (b) UDP messages are limited for practical purposes to about 512 bytes, and (c) when you start to use UDP for real data, you find that a lot of messages get dropped, especially as infrastructure tends to favor TCP over UDP.

0 comments on commit c9a2f8b

Please sign in to comment.
Something went wrong with that request. Please try again.