use Object::Remote::Logging qw( :log );
use Module::Runtime qw(use_module);
-our $VERSION = '0.003001'; # 0.3.1
+our $VERSION = '0.004000'; # 0.4.0
sub new::on {
my ($class, $on, @args) = @_;
Space seperated list of class names to display logs for if logging output is enabled. Default
value is "Object::Remote::Logging" which selects all logs generated by Object::Remote.
-See L<Object::Remote::Logging::Router>.
+See L<Object::Remote::Logging>.
=back
=head1 KNOWN ISSUES
-=over 4
+=over 4
=item Large data structures
serialization the local or remote nodes will be blocked potentially causing all remote
interpreters to block as well under worse case conditions.
-To help deal with this issue it is possible to configure the ulimits for a Perl interpreter
-that is executed by Object::Remote. See C<Object::Remote::Connection> for details.
+To help deal with this issue it is possible to configure resource ulimits for a Perl interpreter
+that is executed by Object::Remote. See C<Object::Remote::Role::Connector::PerlInterpreter>
+for details on the perl_command attribute.
=item User can starve run loop of execution opportunities
=item Deadlocks
-Deadlocks can happen quite easily because of flaws in programs that use Object::Remote or
+Deadlocks can happen quite easily because of flaws in programs that use Object::Remote or
Object::Remote itself so the C<Object::Remote::WatchDog> is available. When used the run
loop will periodically update the watch dog object on the remote Perl interpreter. If the
watch dog goes longer than the configured interval with out being updated then it will
=head1 CONTRIBUTORS
+bfwg - Colin Newell (cpan:NEWELLC) <colin.newell@gmail.com>
+
phaylon - Robert Sedlacek (cpan:PHAYLON) <r.sedlacek@shadowcat.co.uk>
triddle - Tyler Riddle (cpan:TRIDDLE) <t.riddle@shadowcat.co.uk>