On 7/28/2010 1:43 PM, Marc Bollinger wrote:
"and some of them have inherent http capability and aren't used enough
to care about that last 10% efficiency when it means rewriting a bunch
of code with new libraries to get it."
But you're..._adding_ support for memcached to that system. If this were
a system already using memcached, it'd be...speaking memcached. If it
were using a different, external caching system, you'd probably expect
some measure of integration code, or at least testing it if, like
Tyrant, it did speak the same protocol you were expecting. The only
other case would be if you weren't using some external cache already, in
which event you're going to be adding logic, regardless.
I think we don't have the same concept of "the system". Mine is that
unrelated programs may be using the same data and only some of them are
designed around memcache and need its speed. Maybe it would be better
to embed memcache into a traditional http proxy for the things that
don't to avoid having the cache miss logic everywhere.
--
Les Mikesell
lesmikes...@gmail.com
