--- AnyEvent-MP/MP.pm	2009/08/08 21:56:29	1.41
+++ AnyEvent-MP/MP.pm	2009/08/12 21:39:58	1.44
@@ -107,7 +107,7 @@
 
 package AnyEvent::MP;
 
-use AnyEvent::MP::Base;
+use AnyEvent::MP::Kernel;
 
 use common::sense;
 
@@ -117,7 +117,8 @@
 
 use base "Exporter";
 
-our $VERSION = '0.1';
+our $VERSION = $AnyEvent::MP::Kernel::VERSION;
+
 our @EXPORT = qw(
    NODE $NODE *SELF node_of _any_
    resolve_node initialise_node
@@ -503,15 +504,24 @@
 
 =item $guard = mon $port, $rcvport, @msg
 
-Monitor the given port and do something when the port is killed, and
-optionally return a guard that can be used to stop monitoring again.
+Monitor the given port and do something when the port is killed or
+messages to it were lost, and optionally return a guard that can be used
+to stop monitoring again.
+
+C<mon> effectively guarantees that, in the absence of hardware failures,
+that after starting the monitor, either all messages sent to the port
+will arrive, or the monitoring action will be invoked after possible
+message loss has been detected. No messages will be lost "in between"
+(after the first lost message no further messages will be received by the
+port). After the monitoring action was invoked, further messages might get
+delivered again.
 
 In the first form (callback), the callback is simply called with any
 number of C<@reason> elements (no @reason means that the port was deleted
 "normally"). Note also that I<< the callback B<must> never die >>, so use
 C<eval> if unsure.
 
-In the second form (another port given), the other port (C<$rcvport)
+In the second form (another port given), the other port (C<$rcvport>)
 will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on
 "normal" kils nothing happens, while under all other conditions, the other
 port is killed with the same reason.