Skip to content

Commit

Permalink
mention subprocesses in FAQ
Browse files Browse the repository at this point in the history
  • Loading branch information
kraih committed Sep 8, 2016
1 parent f258f69 commit 87b7360
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 5 deletions.
2 changes: 1 addition & 1 deletion Changes
@@ -1,5 +1,5 @@

7.06 2016-09-01
7.06 2016-09-08

7.05 2016-08-29
- Fixed bug in Mojo::IOLoop::Subprocess where EV would steal the subprocess
Expand Down
10 changes: 6 additions & 4 deletions lib/Mojolicious/Guides/FAQ.pod
Expand Up @@ -114,10 +114,12 @@ subroutine is finished, this is called continuation-passing style.

No, it is not possible to magically make Perl code non-blocking. While
L<Mojolicious> has been designed from the ground up for non-blocking I/O and
event loops, taking advantage of this requires specialized code available
through modules like L<Mojo::IOLoop> and L<Mojo::UserAgent>, or third-party
event loops. In the documentation we often refer to this as real-time web, for
more information see also L<Mojolicious::Guides::Cookbook/"REAL-TIME WEB">.
event loops, taking advantage of this requires blocking code to be wrapped in
L<subprocesses|Mojo::IOLoop/"subprocess">, or the use of specialized
non-blocking code available through modules like L<Mojo::IOLoop> and
L<Mojo::UserAgent>, or third-party event loops. In the documentation we often
refer to this as real-time web, for more information see also
L<Mojolicious::Guides::Cookbook/"REAL-TIME WEB">.

=head2 What is an event loop?

Expand Down

0 comments on commit 87b7360

Please sign in to comment.