Hi all!

I've been working recently on a project that involves the totally-awesome
MetaCPAN (metacpan.org, search.metacpan.org).
MetaCPAN itself has a defined, public API, to get information in a RESTful
manner, and I've written a module that lets you interact with the API
easily.
It supports both all the allowed methods of MetaCPAN, but also intermediate
methods that try to DWIM for a user.

use MetaCPAN::API;
my $mcpan  = MetaCPAN::API->new();
my $author = $mcpan->search_author_pauseid("XSAWYERX");
my $dist   = $mcpan->search_dist("Moose");

Before I upload the code (which is already written, for all methods MetaCPAN
allows, and more) to CPAN and Github, I just wanted to know that taking a
top-level namespace here makes sense and get any input on it. Here are some
notes:
1. It does not use Mechanize, LWP, or anything for which the WWW:: namespace
would make sense.
2. Tiny and concise, as to be an official completely workable API
implementation (currently using Mouse - or rather, Any::Moose - and
HTTP::Tiny).
3. I prefer not to bury this inside a low namespace
(WebService::PerlRelated::MetaCPAN::API::Implementation::Sawyer).
4. I've spoken to Olaf Alders from MetaCPAN and he assured me they have no
problem with the name, and that they would use it themselves once it's out.

Thank you,
Sawyer.

Reply via email to