[ViewVC] Diff of: cvs/AnyEvent-MP/MP/Intro.pod

Comparing AnyEvent-MP/MP/Intro.pod (file contents):
Revision 1.55 by root, Thu Mar 22 00:48:29 2012 UTC vs.
Revision 1.56 by root, Thu Mar 22 23:47:02 2012 UTC

 network, often the same string as used for the C<binds> parameter of the
 other node. The need for seeds is easy to explain: I<somehow> the nodes
 of an aemp network have to find each other, and often this means over the
 internet. So broadcasts are out.
-Instead, a node usually specifies the addresses of a few (for redundancy)
+Instead, a node usually specifies the addresses of one or few (for
-other nodes, some of which should be up. Two nodes can set each other as
+redundancy) other nodes, some of which should be up. Two nodes can set
-seeds without any issues. You could even specify all nodes as seeds for
+each other as seeds without any issues. You could even specify all nodes
-all nodes, for total redundancy. But the common case is to have some more
+as seeds for all nodes, for total redundancy. But the common case is to
-or less central, stable servers running seed services for other nodes.
+have some more or less central, stable servers running seed services for
+other nodes.
 All you need to do to ensure that an AnyEvent::MP network connects
 together is to make sure that all seed nodes are connected together via
 their seed connections, i.e., all connections from seed nodes to I<their>
-seed nodes form a connected graph. It's not necessary (but common) for a
+seed nodes form a connected graph.
-seed node to list all other seed nodes as seeds. The rest of the nodes in
-the network simply specify one or more of the seed nodes in their seed
-list.
-The simplest way to do that would be for all nodes to specify a single
-node as seed node, and you would get a star topology. If you specify all
-nodes as seed nodes, you get a fully meshed network (that's what previous
-releases of AnyEvent::MP actually did).
 A node tries to keep connections open to all of it's seed nodes at all
 times, while other connections are made on demand only.
+The simplest way to do that would be for all nodes to use the same seed
+nodes: seed nodes would seed each other, and all other nodes would connect
+to the seed nodes.
 All of this ensures that the network stays one network - even if all the
 nodes in one half of the net are separated from the nodes in the other
 half by some network problem, once that is over, they will eventually
 become a single network again.
 Without further ado, here is the chat server (to run it, we assume the
 set-up explained earlier, with a separate F<aemp run seed> node):
    use common::sense;
    use AnyEvent::MP;
-   use AnyEvent::MP::Global;
    configure;
    my %clients;
 new function, C<spawn>:
 #todo#
    use common::sense;
    use AnyEvent::MP;
-   use AnyEvent::MP::Global;
    my $nick = shift;
    configure;

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing AnyEvent-MP/MP/Intro.pod (file contents): Revision 1.55 by root, Thu Mar 22 00:48:29 2012 UTC vs. Revision 1.56 by root, Thu Mar 22 23:47:02 2012 UTC

Diff Legend

Comparing AnyEvent-MP/MP/Intro.pod (file contents):
Revision 1.55 by root, Thu Mar 22 00:48:29 2012 UTC vs.
Revision 1.56 by root, Thu Mar 22 23:47:02 2012 UTC