[Maypole] Maypole::Cache

[Simon Cozens]

Perrin Harkins:
> simple MySQL query.  They have a clean API, but no one else has adopted
> it, so it's not very useful.

You see it as not useful, I see it as room for improvement.

> IPC::MM and BerkeleyDB also have acceptable performance for shared data,
 
I'm sorry, but I believe in two principles as far as Maypole goes:
    1) Making things as easy as possible, and
    2) Giving the user the choice.

Maypole::Cache is designed to do these things. It gives the user the choice by
allowing them to easily switch between backend cache implementations; it makes
things as easy as possible by using a caching framework which means that
switching implementations is not going to cause a problem. As such, it fulfils
its goals perfectly. So you are not going to sway me on that score.

If you feel that the Cache::Cache modules do not have acceptable performance
for you, then
    1) Cache::Cache is the problem, whereas Maypole::Cache is doing precisely
what it was designed to do, and
    2) I look forward to seeing your faster implementations on CPAN. 
    
In the meantime, questions about why such-and-such a Cache::Cache module is
not as fast as something else are as related to Maypole as "How do I do this
in Class::DBI" and "how do I do this in Template Toolkit".

-- 
Asynchronous inputs are at the root of our race problems.
		-- D. Winker and F. Prosser