Skip Menu |

This queue is for tickets about the Event-RPC CPAN distribution.

Report information
The Basics
Id: 83826
Status: new
Priority: 0/
Queue: Event-RPC

People
Owner: Nobody in particular
Requestors: x.guimard [...] free.fr
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: 1.03
Fixed in: (no value)



Subject: Spelling errors in pod
Hi, here are some little spelling errors: --- a/lib/Event/RPC/Client.pm +++ b/lib/Event/RPC/Client.pm @@ -473,8 +473,8 @@ $rpc_client->connect; - #-- And now use classes and methods the server - #-- allows to access via RPC, here My::TestModule + #-- And now use classes and methods to which the + #-- server allows access via RPC, here My::TestModule #-- from the Event::RPC::Server manpage SYNPOSIS. my $obj = My::TestModule->new( data => "foobar" ); print "obj says hello: ".$obj->hello."\n"; --- a/lib/Event/RPC/Server.pm +++ b/lib/Event/RPC/Server.pm @@ -514,7 +514,7 @@ ... }, -Each class which should be accessable for clients needs to +Each class which should be accessible for clients needs to be listed here at the first level, assigned a hash of methods allowed to be called. Event::RPC disuinguishes three types of methods by classifying their return value: @@ -756,7 +756,7 @@ and manage the main loop stuff on your o By default the network listeners are bound to all interfaces in the system. Use the host option to bind to a specific -interface, e.g. "localhost" if you efficently want to prevent +interface, e.g. "localhost" if you efficiently want to prevent network clients from accessing your server. =item B<load_modules>