mention the blocking resolver

mojolicious · Nov 1, 2014 · c3290fa · c3290fa
1 parent fba99a9
commit c3290fa
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/Changes b/Changes
@@ -1,5 +1,5 @@
 
-5.57  2014-11-01
+5.57  2014-11-02
 
 5.56  2014-10-29
   - Deprecated Mojo::Collection::AUTOLOAD in favor of Mojo::Collection::pluck.

diff --git a/lib/Mojo/IOLoop.pm b/lib/Mojo/IOLoop.pm
@@ -314,6 +314,10 @@ scalable C<select>.
   LIBEV_FLAGS=4   # epoll (Linux)
   LIBEV_FLAGS=8   # kqueue (*BSD, OS X)
 
+Connections are established non-blocking, but name resolution needs to be
+performed blocking, so you should limit concurrency if resolver timeouts are a
+possibility.
+
 The event loop will be resilient to time jumps if a monotonic clock is
 available through L<Time::HiRes>. A TLS certificate and key are also built
 right in, to make writing test servers as easy as possible. Also note that for