On Wed, Jul 14, 2010 at 6:59 PM, Leonardo Rochael Almeida
leoroch...@gmail.com wrote:
On Wed, Jul 14, 2010 at 19:22, Benji York be...@benjiyork.com wrote:
[...]
Not surprising really.
What could be surprising is that, since the objects are not in the
object cache or the ZEO cache, how can
On Wed, Jul 14, 2010 at 12:22 AM, Leonardo Rochael Almeida
leoroch...@gmail.com wrote:
The attached patch adds such a warning, and also reveals where Zope2
commits the same sins. If there are no objections I'll commit it to
2.12 and trunk.
Thanks for committing it.
Finally, I'd like to ask
Am 15.07.2010, 10:35 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:
But to avoid any such issues, I'll restrain myself from doing any
further feature changes to Zope 2.12. 2.13 is closing in fast enough
and there's always a 2.14.
I'll check ZPsycopgDA and make sure we look at the
Summary of messages to the zope-tests list.
Period Wed Jul 14 12:00:00 2010 UTC to Thu Jul 15 12:00:00 2010 UTC.
There were 70 messages: 6 from Zope Tests, 2 from buildbot at
enfoldsystems.com, 4 from buildbot at pov.lt, 17 from buildbot at
winbot.zope.org, 13 from ccomb at free.fr, 28 from
Hi Sebastian,
Why don’t you consider to use memcached for caching the results instead of
using sessions? By using this, Zeo server/Zeo clients restart wont affect
cached data.
HTH,
Dragos
On Sun, Jul 11, 2010 at 8:41 AM, Sebastian Tiedtke s...@mdvtts.com wrote:
Hi all,
We're working on
On 7/15/10 17:03 , Dragos Chirila wrote:
Hi Sebastian,
Why don’t you consider to use memcached for caching the results instead
of using sessions? By using this, Zeo server/Zeo clients restart wont
affect cached data.
or plone.memoize, using either a RAMCache or memcached as backend.
