Tim Bunce wrote:
I'm looking to build a very thin wrapper around libmemcached
(http://tangent.org/552/libmemcached.html)
a high-performance feature-rich interface to memcached.
[...]
I was thinking in terms of a low-level 'thin' extension called
Lib::libmemcached with separate pure-perl modules implementing the
Cache
and Cache::Cache interfaces.
So, here's the point: does anyone have any good objections to my
establishing a new precident by using the Lib:: namespace for this?
(Or perhaps CLib:: or SysLib:: or ...)
I was wondering why you wanted to build yet another Memcached module
given there is already Cache::Memcached::XS, but now I understand:
you want to do something similar to what Paul Marquess did with
Compress::Zlib when he splitted it between a high-level Perl frontend
(Compress::Zlib) and a low-level driver (Compress::Raw::Zlib), which
allowed him to provide bzip2 support (Compress::Raw::Bzip2).
It's also similar to the Win32 situation: Win32API::* modules provide
low-level API, while Win32::* provide high-level API.
IMHO, "Lib" doesn't carry as much information as "Raw" or even "API",
given the already existing modules. So possible namespaces are:
Cache::Raw::Memcached or CacheAPI::Memcached.
Or, if you don't want to be related to the Cache:: namespace,
Memcached::Raw or Memcached::API.
--
Sébastien Aperghis-Tramoni
Close the world, txEn eht nepO.
