X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=scpubgit%2FObject-Remote.git;a=blobdiff_plain;f=lib%2FObject%2FRemote%2FLogging%2FRouter.pm;h=84a562fad483526b84e56e510526df2317fb4947;hp=16c9774553112e120c3a84c242209fe6a163a272;hb=052976d4a389b826a9551909492f3fc2f2312c88;hpb=1a90d0eeb2ed492e0f7f84e95c67161491d8f79e

diff --git a/lib/Object/Remote/Logging/Router.pm b/lib/Object/Remote/Logging/Router.pm
index 16c9774..84a562f 100644
--- a/lib/Object/Remote/Logging/Router.pm
+++ b/lib/Object/Remote/Logging/Router.pm
@@ -7,8 +7,6 @@ use Sys::Hostname;
 with 'Log::Contextual::Role::Router';
 with 'Object::Remote::Role::LogForwarder';
 
-#lookup table for package names that should not
-#be forwarded across Object::Remote connections
 has _connections => ( is => 'ro', required => 1, default => sub { [] } );
 has _remote_metadata => ( is => 'rw' );
 
@@ -49,7 +47,7 @@ sub _get_loggers {
 sub _invoke_logger {
   my ($self, $logger, $level_name, $content, $metadata) = @_;
   #Invoking the logger like this gets all available data to the
-  #logging object with out losing any information from the structure.
+  #logging object with out losing any information from the datastructure.
   #This is not a backwards compatible way to invoke the loggers
   #but it enables a lot of flexibility in the logger.
   #The l-c router could have this method invoke the logger in