removed IO::Async recipe for now

mojolicious · Jun 8, 2012 · 74ff0ac · 74ff0ac
1 parent a08e4ee
commit 74ff0ac
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 22 deletions.
diff --git a/Changes b/Changes
@@ -1,5 +1,5 @@
 
-2.99  2012-06-08
+2.99  2012-06-09
   - Improved message parser performance slightly.
   - Improved documentation. (ichesnokov, sri)
   - Improved tests.

diff --git a/lib/Mojolicious/Guides/Cookbook.pod b/lib/Mojolicious/Guides/Cookbook.pod
@@ -625,27 +625,7 @@ which can be combined to solve some of hardest problems in web development.
 
 Internally the L<Mojo::IOLoop> reactor can use multiple event loop backends,
 L<EV> for example will be automatically used if installed. Which in turn
-allows event loops like L<IO::Async> to just work.
-
-  use Mojolicious::Lite;
-  use EV;
-  use IO::Async::Loop::EV;
-  use IO::Async::Timer::Absolute;
-
-  my $loop = IO::Async::Loop::EV->new;
-
-  # Wait 3 seconds before rendering a response
-  get '/' => sub {
-    my $self = shift;
-    $loop->add(IO::Async::Timer::Absolute->new(
-      time      => time + 3,
-      on_expire => sub { $self->render(text => 'Delayed by 3 seconds!') }
-    ));
-  };
-
-  app->start;
-
-Same for L<AnyEvent>.
+allows event loops like L<AnyEvent> to just work.
 
   use Mojolicious::Lite;
   use EV;