| … | |
… | |
| 116 | seed node that blocks for long periods will slow down everybody else. |
116 | seed node that blocks for long periods will slow down everybody else. |
| 117 | |
117 | |
| 118 | =item seeds - C<host:port> |
118 | =item seeds - C<host:port> |
| 119 | |
119 | |
| 120 | Seeds are transport endpoint(s) (usually a hostname/IP address and a |
120 | Seeds are transport endpoint(s) (usually a hostname/IP address and a |
| 121 | TCP port) of nodes thta should be used as seed nodes. |
121 | TCP port) of nodes that should be used as seed nodes. |
| 122 | |
122 | |
| 123 | The nodes listening on those endpoints are expected to be long-running, |
123 | The nodes listening on those endpoints are expected to be long-running, |
| 124 | and at least one of those should always be available. When nodes run out |
124 | and at least one of those should always be available. When nodes run out |
| 125 | of connections (e.g. due to a network error), they try to re-establish |
125 | of connections (e.g. due to a network error), they try to re-establish |
| 126 | connections to some seednodes again to join the network. |
126 | connections to some seednodes again to join the network. |
| … | |
… | |
| 523 | delivered again. |
523 | delivered again. |
| 524 | |
524 | |
| 525 | Inter-host-connection timeouts and monitoring depend on the transport |
525 | Inter-host-connection timeouts and monitoring depend on the transport |
| 526 | used. The only transport currently implemented is TCP, and AnyEvent::MP |
526 | used. The only transport currently implemented is TCP, and AnyEvent::MP |
| 527 | relies on TCP to detect node-downs (this can take 10-15 minutes on a |
527 | relies on TCP to detect node-downs (this can take 10-15 minutes on a |
| 528 | non-idle connection, and usually around two hours for idle conenctions). |
528 | non-idle connection, and usually around two hours for idle connections). |
| 529 | |
529 | |
| 530 | This means that monitoring is good for program errors and cleaning up |
530 | This means that monitoring is good for program errors and cleaning up |
| 531 | stuff eventually, but they are no replacement for a timeout when you need |
531 | stuff eventually, but they are no replacement for a timeout when you need |
| 532 | to ensure some maximum latency. |
532 | to ensure some maximum latency. |
| 533 | |
533 | |
| … | |
… | |
| 565 | } |
565 | } |
| 566 | |
566 | |
| 567 | $node->monitor ($port, $cb); |
567 | $node->monitor ($port, $cb); |
| 568 | |
568 | |
| 569 | defined wantarray |
569 | defined wantarray |
| 570 | and $cb += 0 |
|
|
| 571 | and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) } |
570 | and ($cb += 0, AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }) |
| 572 | } |
571 | } |
| 573 | |
572 | |
| 574 | =item $guard = mon_guard $port, $ref, $ref... |
573 | =item $guard = mon_guard $port, $ref, $ref... |
| 575 | |
574 | |
| 576 | Monitors the given C<$port> and keeps the passed references. When the port |
575 | Monitors the given C<$port> and keeps the passed references. When the port |
| … | |
… | |
| 775 | AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node |
774 | AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node |
| 776 | == aemp node, Erlang process == aemp port), so many of the documents and |
775 | == aemp node, Erlang process == aemp port), so many of the documents and |
| 777 | programming techniques employed by Erlang apply to AnyEvent::MP. Here is a |
776 | programming techniques employed by Erlang apply to AnyEvent::MP. Here is a |
| 778 | sample: |
777 | sample: |
| 779 | |
778 | |
| 780 | http://www.Erlang.se/doc/programming_rules.shtml |
779 | http://www.erlang.se/doc/programming_rules.shtml |
| 781 | http://Erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4 |
780 | http://erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4 |
| 782 | http://Erlang.org/download/Erlang-book-part1.pdf # chapters 5 and 6 |
781 | http://erlang.org/download/erlang-book-part1.pdf # chapters 5 and 6 |
| 783 | http://Erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5 |
782 | http://erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5 |
| 784 | |
783 | |
| 785 | Despite the similarities, there are also some important differences: |
784 | Despite the similarities, there are also some important differences: |
| 786 | |
785 | |
| 787 | =over 4 |
786 | =over 4 |
| 788 | |
787 | |
