Hello all,
I'm writing a module that I dubbed Net::Vimeo::API for now. It's
rather self-explanatory, but just to make sure: it's supposed to be a
perl module for interfacing with the full Vimeo API (www.vimeo.com). I
am thinking about publishing it on CPAN.
It roughly goes something like this:
Chris:
I'm not sure of the best answer here, though I do know that top-level
namespaces (like Vimeo::API) are generally frowned upon.
A cursory search of API turns up:
- WWW::Facebook::API
- WWW::Bebo::API
As the first two results. On the other hand, some people have used the
namespace
On Tue, Mar 10, 2009 at 10:05 AM, Jonathan Yu jonathan.i...@gmail.com wrote:
WWW::Vimeo.
That would be my choice. Adding API seems redundant.
David
On 10 Mar 2009, at 14:23, David Golden wrote:
On Tue, Mar 10, 2009 at 10:05 AM, Jonathan Yu
jonathan.i...@gmail.com wrote:
WWW::Vimeo.
That would be my choice. Adding API seems redundant.
Agreed. That's in line with the de-facto standard.
--
Andy Armstrong, Hexten
On Tue, Mar 10, 2009 at 3:27 PM, Andy Armstrong a...@hexten.net wrote:
On 10 Mar 2009, at 14:23, David Golden wrote:
On Tue, Mar 10, 2009 at 10:05 AM, Jonathan Yu jonathan.i...@gmail.com
wrote:
WWW::Vimeo.
That would be my choice. Adding API seems redundant.
Agreed. That's in line with
On Tue, Mar 10, 2009 at 6:23 AM, David Golden da...@hyperbolic.net wrote:
On Tue, Mar 10, 2009 at 10:05 AM, Jonathan Yu jonathan.i...@gmail.com
wrote:
WWW::Vimeo.
That would be my choice. Adding API seems redundant.
I agree about dropping API, but prefer Net. WWW to me suggests web
On Tue, Mar 10, 2009 at 2:38 PM, Bill Ward b...@wards.net wrote:
I agree about dropping API, but prefer Net. WWW to me suggests web browsers
and HTML.
There are certainly plenty of web-service interface modules popping up
under Net. Personally, I wish people used that only for lower-level
