On Dec 31 2008, 5:01 pm, Tycon adie...@gmail.com 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
On Dec 31, 3:19 pm, Tycon adie...@gmail.com wrote:
whatever you end up doing NEVER EVER DO a flush_all on memcached.
Memcached is a global system service, it is not your private scratch
pad.
yessir !
though I've never considered a single memcached process as a global
service, like say
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) ?
While it is possible to have a memcached server dedicated to one
application, you can't assume this is the default.
On Dec 31, 12:48 pm, Michael Bayer
Cause if I use this setting in development.ini :
beaker.session.type = ext:memcached
beaker.session.url = 127.0.0.1:11211
then if I try to access the session global, I get this error:
NotImplementedError: Memcache caching does not support iteration of
all cache keys
This is raised from Module
On Tue, Dec 30, 2008 at 1:10 PM, Tycon adie...@gmail.com wrote:
So I guess no one is actually using memcached for storing sessions ?
Or of you do, do you define your own memcached interface instead of
the
Beaker memcached interface for session storage ?
I haven't use memcached, and I doubt
Let me clarify that using memcached in beaker doesn't work ONLY FOR
STORING SESSIONS.
It does work for regular caching in beaker (e.g. using @beaker_cache
decorator
to cache controller actions etc).
This is not a bug, it's basically an incorrect implementation, which
uses wrong design and is
On Dec 30, 2008, at 3:09 PM, Tycon wrote:
It does work for regular caching in beaker (e.g. using @beaker_cache
decorator
to cache controller actions etc).
This is not a bug, it's basically an incorrect implementation, which
uses wrong design and is completely untested. For storing sessions in
On 4/27/07, Cliff Wells [EMAIL PROTECTED] wrote:
On Fri, 2007-04-27 at 17:24 -0700, Shannon -jj Behrens wrote:
This topic is covered very nicely in Building Scalable Web Sites and
Scalable Internet Architectures.
Okay, one more plug for these books and there's going to be a demand for
On 4/24/07, Damjan [EMAIL PROTECTED] wrote:
You can store sessions (or the needed info) in just cookies, a
database (MySQL, Postgresql, etc) or memcached. It's not neccesseary
to store the session in files.
Agreed. memcached is very popular for scalable session servers, not
just in the
On Fri, 2007-04-27 at 17:24 -0700, Shannon -jj Behrens wrote:
This topic is covered very nicely in Building Scalable Web Sites and
Scalable Internet Architectures.
Okay, one more plug for these books and there's going to be a demand for
full disclosure ;-)
Cliff
After some digging I came up with the following solution:
In config/middleware.py at the top op make_app I've added the
following lines:
from sqla import SQLAlchemyNamespaceManager
app_conf['session_namespace_class'] = SQLAlchemyNamespaceManager
app_conf['session_dburi'] =
11 matches
Mail list logo