--- AnyEvent-MP/MP.pm	2009/08/15 04:12:38	1.56
+++ AnyEvent-MP/MP.pm	2009/08/15 04:34:34	1.57
@@ -683,52 +683,6 @@
 
 =back
 
-=head1 NODE MESSAGES
-
-Nodes understand the following messages sent to them. Many of them take
-arguments called C<@reply>, which will simply be used to compose a reply
-message - C<$reply[0]> is the port to reply to, C<$reply[1]> the type and
-the remaining arguments are simply the message data.
-
-While other messages exist, they are not public and subject to change.
-
-=over 4
-
-=cut
-
-=item lookup => $name, @reply
-
-Replies with the port ID of the specified well-known port, or C<undef>.
-
-=item devnull => ...
-
-Generic data sink/CPU heat conversion.
-
-=item relay => $port, @msg
-
-Simply forwards the message to the given port.
-
-=item eval => $string[ @reply]
-
-Evaluates the given string. If C<@reply> is given, then a message of the
-form C<@reply, $@, @evalres> is sent.
-
-Example: crash another node.
-
-   snd $othernode, eval => "exit";
-
-=item time => @reply
-
-Replies the the current node time to C<@reply>.
-
-Example: tell the current node to send the current time to C<$myport> in a
-C<timereply> message.
-
-   snd $NODE, time => $myport, timereply => 1, 2;
-   # => snd $myport, timereply => 1, 2, <time>
-
-=back
-
 =head1 AnyEvent::MP vs. Distributed Erlang
 
 AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node