On Aug 23, 2007, at 6:16 PM, Mike Orr wrote:
At some point I got a DeprecationWarning that all cache_ variables
should be changed to cache.. Looking back, it must have been
cache_enabled that triggered it. So I changed the underscores to
dots, and later noticed a None directory in my
Tomasz Nazar wrote:
On 8/24/07, *Christoph Haas* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
As I understand 'c' is always reset before any controller's
action - what is
not fun for me, as in my app one user request/click is often 2
(or more)
Pylons
On Aug 24, 2007, at 2:56 AM, Dan Korostelev wrote:
Yeah, I also worked around the problem this way, but I don't like
it. Looks like there's a bug in Routes. Thanks for information.
There's no bug in routes, this is exactly how it works, and how the
docs indicate it works. From the docs
On Aug 24, 2007, at 4:15 PM, Cliff Wells wrote:
Memcached seems the easiest (and probably best) solution. As Philip
mentions, however, it isn't well-documented how to use Beaker with
Memcached. If you decide to go this route, maybe update the wiki?
I'd highly suggest memcached rather than
On 8/25/07, Ben Bangert [EMAIL PROTECTED] wrote:
I'd highly suggest memcached rather than database backend. It's easy
to setup, and of course, very fast. :)
Yes, but as far as I know, memcached objects can be always replaced,
that is, you cannot define an object to be persistent, can you?
On 8/25/07, Jose Galvez [EMAIL PROTECTED] wrote:
Tomasz Nazar wrote:
On 8/24/07, Christoph Haas [EMAIL PROTECTED] wrote:
As I understand 'c' is always reset before any controller's action -
what is
not fun for me, as in my app one user request/click is often 2 (or
more)
On Sat, 2007-08-25 at 20:24 +0300, Pekka Jääskeläinen wrote:
On 8/25/07, Ben Bangert [EMAIL PROTECTED] wrote:
I'd highly suggest memcached rather than database backend.
It's easy
to setup, and of course, very fast. :)
Yes, but as far as I know, memcached objects can
On Aug 22, 2007, at 10:16 PM, Mike Orr wrote:
I'm using Session.mapper in my application and find it superior to
the regular mapper.
According to the page history, Mike Bayer took it out to avoid
confusing newbies who might think it'srecommended rather than
optional. I put it back in with a
now I'll have to take a closer look at Session.mapper because it looks
like your implying that is does something other then what the old assign
mapper did. I have a project right now where I'm using Session.mapper
and I've not hit any problems yet. And it does let me do
from model import Mytable
Ben, I've just read the Session.mapper docs and I'm not sure what your
concerns are. Are you concerned with its use? or that putting it in the
tutorial will confuse new users?
Jose
Ben Bangert wrote:
On Aug 22, 2007, at 10:16 PM, Mike Orr wrote:
I'm using Session.mapper in my application
10 matches
Mail list logo
