RPC-Async 1.05 Latest
Kwalitee Issues
No Core Issues.
- meta_yml_declares_perl_version
 - 
        
If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.
 - has_meta_json
 - 
        
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
 
- meta_yml_has_repository_resource
 - 
        
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
 - has_separate_license_file
 - 
        
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
 - has_security_doc
 - 
        
Add SECURITY(.pod|md). See Software::Security::Policy.
 - security_doc_contains_contact
 - 
        
Add SECURITY(.pod|md) and add a contact address. See Software::Security::Policy.
 - has_contributing_doc
 - 
        
Add CONTRIBUTING(.pod|md). See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.
 
Modules
| Name | Abstract | Version | View | 
|---|---|---|---|
| RPC::Async | Asynchronous RPC framework | 1.05 | metacpan | 
| RPC::Async::Client | client side of asynchronous RPC framework | 1.05 | metacpan | 
| RPC::Async::Coderef | wrapper class to ensure that coderefs are unmapped and discarded on the client side when garbage collected on the server side | 1.05 | metacpan | 
| RPC::Async::Server | server side of asynchronous RPC framework | 1.05 | metacpan | 
| RPC::Async::URL | Utility functions to handle URLs | 1.05 | metacpan | 
| RPC::Async::Util | util module of the asynchronous RPC framework | 1.05 | metacpan |