RMI 0.10 Latest
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
Fix the version numbers so that version::is_lax($version) returns true.
- lib/RMI/Client.pm: HASH(0x6f5f510)
- lib/RMI/Client/ForkedPipes.pm: HASH(0x6f60488)
- lib/RMI/Client/Tcp.pm: HASH(0x6f60398)
- lib/RMI/Node.pm: HASH(0x6f600c8)
- lib/RMI/ProxyObject.pm: HASH(0x6f60338)
- lib/RMI/ProxyReference.pm: HASH(0x6f602f0)
- lib/RMI/Server.pm: HASH(0x6f604a0)
- lib/RMI/Server/ForkedPipes.pm: HASH(0x6f603c8)
- lib/RMI/Server/Tcp.pm: HASH(0x6f60440)
Add 'use warnings' (or its equivalents) to all modules (this will require perl > 5.6), or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
|RMI||Remote Method Invocation with transparent proxies||0.10||metacpan|
|RMI::Client||connection to an RMI::Server||metacpan|
|RMI::Client::ForkedPipes||an RMI::Client implementation with a private out-of-process server||metacpan|
|RMI::Client::Tcp||an RMI::Client implementation using TCP/IP sockets||metacpan|
|RMI::Node||base class for RMI::Client and RMI::Server||metacpan|
|RMI::ProxyObject||used internally by RMI for "stub" objects||metacpan|
|RMI::ProxyReference||used internally by RMI to tie references||metacpan|
|RMI::Server||service RMI::Client requests from another process||metacpan|
|RMI::Server::ForkedPipes||service RMI::Client::ForkedPipes requests||metacpan|
|RMI::Server::Tcp||service RMI::Client::Tcp requests||metacpan|