Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
refer consistently to inactivity timeouts
  • Loading branch information
kraih committed Feb 27, 2012
1 parent df7ed5f commit da4c517
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 7 deletions.
3 changes: 0 additions & 3 deletions lib/Mojo/IOLoop.pm
Expand Up @@ -580,9 +580,6 @@ and the loop can be restarted by running C<start> again.
Get L<Mojo::IOLoop::Stream> object for id or turn object into a connection.
Note that this method is EXPERIMENTAL and might change without warning!
# Increase timeout for the connection of a transaction to 300 seconds
Mojo::IOLoop->stream($tx->connection)->timeout(300);
=head2 C<timer>
my $id = Mojo::IOLoop->timer(5 => sub {...});
Expand Down
8 changes: 4 additions & 4 deletions lib/Mojolicious/Controller.pm
Expand Up @@ -929,10 +929,10 @@ EXPERIMENTAL and might change without warning!
# Send "Ping" frame
$c->send([1, 0, 0, 0, 9, 'Hello World!']);
For mostly idle WebSockets you might also want to increase the connection
For mostly idle WebSockets you might also want to increase the inactivity
timeout, which usually defaults to C<15> seconds.
# Increase timeout for current connection to 300 seconds
# Increase inactivity timeout for connection to 300 seconds
Mojo::IOLoop->stream($c->tx->connection)->timeout(300);
=head2 C<session>
Expand Down Expand Up @@ -1055,10 +1055,10 @@ invoked once all data has been written.
});
});
For Comet (C<long polling>) you might also want to increase the connection
For Comet (C<long polling>) you might also want to increase the inactivity
timeout, which usually defaults to C<15> seconds.
# Increase timeout for current connection to 300 seconds
# Increase inactivity timeout for connection to 300 seconds
Mojo::IOLoop->stream($c->tx->connection)->timeout(300);
=head2 C<write_chunk>
Expand Down

0 comments on commit da4c517

Please sign in to comment.