X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=scpubgit%2FObject-Remote.git;a=blobdiff_plain;f=lib%2FObject%2FRemote.pm;h=cc4a013c7a22f6a73a5e449816a5dfa52325b47d;hp=2c8c096ff2ccd8a343f5a4be83e398f4e6e95583;hb=bb679f1669ee8f483be9bee220154e1ac6ebb677;hpb=b0ec7e3b19d47b9ba5a864f5077d0dc8030834cc diff --git a/lib/Object/Remote.pm b/lib/Object/Remote.pm index 2c8c096..cc4a013 100644 --- a/lib/Object/Remote.pm +++ b/lib/Object/Remote.pm @@ -5,7 +5,7 @@ use Object::Remote::Handle; use Object::Remote::Logging qw( :log ); use Module::Runtime qw(use_module); -our $VERSION = '0.003001'; # 0.3.1 +our $VERSION = '0.003001_01'; # 0.3.1 sub new::on { my ($class, $on, @args) = @_; @@ -163,7 +163,7 @@ See L. =head1 KNOWN ISSUES -=over 4 +=over 4 =item Large data structures @@ -204,7 +204,7 @@ timeouts taking longer than configured. =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 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