--- AnyEvent/lib/AnyEvent.pm	2010/04/12 02:50:31	1.320
+++ AnyEvent/lib/AnyEvent.pm	2010/05/20 21:22:20	1.323
@@ -9,7 +9,7 @@
 
    use AnyEvent;
 
-   # if you prefer function calls, look at the L<AE> manpage for
+   # if you prefer function calls, look at the AE manpage for
    # an alternative API.
 
    # file handle or descriptor readable
@@ -1084,60 +1084,48 @@
 
 Provides rich asynchronous DNS resolver capabilities.
 
-=item L<AnyEvent::HTTP>
+=item L<AnyEvent::HTTP>, L<AnyEvent::IRC>, L<AnyEvent::XMPP>, L<AnyEvent::GPSD>, L<AnyEvent::IGS>, L<AnyEvent::FCP>
 
-A simple-to-use HTTP library that is capable of making a lot of concurrent
-HTTP requests.
-
-=item L<AnyEvent::HTTPD>
-
-Provides a simple web application server framework.
-
-=item L<AnyEvent::FastPing>
-
-The fastest ping in the west.
+Implement event-based interfaces to the protocols of the same name (for
+the curious, IGS is the International Go Server and FCP is the Freenet
+Client Protocol).
+
+=item L<AnyEvent::Handle::UDP>
+
+Here be danger!
+
+As Pauli would put it, "Not only is it not right, it's not even wrong!" -
+there are so many things wrong with AnyEvent::Handle::UDP, most notably
+it's use of a stream-based API with a protocol that isn't streamable, that
+the only way to improve it is to delete it.
+
+It features data corruption (but typically only under load) and general
+confusion. On top, the author is not only clueless about UDP but also
+fact-resistant - some gems of his understanding: "connect doesn't work
+with UDP", "UDP packets are not IP packets", "UDP only has datagrams, not
+packets", "I don't need to implement proper error checking as UDP doesn't
+support error checking" and so on - he doesn't even understand what's
+wrong with his module when it is explained to him.
 
 =item L<AnyEvent::DBI>
 
-Executes L<DBI> requests asynchronously in a proxy process.
+Executes L<DBI> requests asynchronously in a proxy process for you,
+notifying you in an event-bnased way when the operation is finished.
 
 =item L<AnyEvent::AIO>
 
-Truly asynchronous I/O, should be in the toolbox of every event
-programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
-together.
-
-=item L<AnyEvent::BDB>
-
-Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
-L<BDB> and AnyEvent together.
-
-=item L<AnyEvent::GPSD>
+Truly asynchronous (as opposed to non-blocking) I/O, should be in the
+toolbox of every event programmer. AnyEvent::AIO transparently fuses
+L<IO::AIO> and AnyEvent together, giving AnyEvent access to event-based
+file I/O, and much more.
 
-A non-blocking interface to gpsd, a daemon delivering GPS information.
-
-=item L<AnyEvent::IRC>
-
-AnyEvent based IRC client module family (replacing the older Net::IRC3).
-
-=item L<AnyEvent::XMPP>
-
-AnyEvent based XMPP (Jabber protocol) module family (replacing the older
-Net::XMPP2>.
-
-=item L<AnyEvent::IGS>
-
-A non-blocking interface to the Internet Go Server protocol (used by
-L<App::IGS>).
-
-=item L<Net::FCP>
+=item L<AnyEvent::HTTPD>
 
-AnyEvent-based implementation of the Freenet Client Protocol, birthplace
-of AnyEvent.
+A simple embedded webserver.
 
-=item L<Event::ExecFlow>
+=item L<AnyEvent::FastPing>
 
-High level API for event-based execution flow control.
+The fastest ping in the west.
 
 =item L<Coro>
 
@@ -1161,7 +1149,7 @@
 
 use Carp ();
 
-our $VERSION = '5.26';
+our $VERSION = '5.261';
 our $MODEL;
 
 our $AUTOLOAD;