On Dec 31 2008, 5:01 pm, Tycon <[email protected]> wrote:
> if it's not a system service then why does it have it's own /etc/
> init.d file
> (the way it's packaged for most major distributions) ?

oh I always just build it from source :) .    that theres an /etc/
init.d entry indicates its a decision of those distros to have a
single "memcached daemon" running, its not a decision of memcached.
I've read through the memcached website very thoroughly regarding this
question and I don't see any guidelines on this issue in either
direction.  I wouldn't think memcached itself has much of an opinion
on how its run.   I would almost guarantee that high volume websites
which use memcached do not multipurpose a single memcached instance
across multiple unrelated applications, though...apart from the
difficulty of multiple performance profiles affecting the single
memcached process in different ways, why bother taking the risk that
two different applications might use the same keynames for different
purposes.

> While it is possible to have a memcached server dedicated to one
> application, you can't assume this is the default.

with that said, of course I agree on this.   I made it pretty clear in
the CHANGELOG that the remove() method with the memcached backend now
does flush_all(), which is not a method that's called by the library
except by the erroneous usage of it in Session, and I've sent Ben a
patch which changes Session to store a single dict on one key in the
namespace regardless of backend so namespace.remove() would not be
used.   I've also advised that namespace.remove(), just like
namespace.keys(), raise a NotImplementedError() when using the
memcached backend.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to