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.
Wic
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 wrote:
> Hi all,
>
> We're working on a large scal
On Wed, Jul 14, 2010 at 6:59 PM, Leonardo Rochael Almeida
wrote:
> On Wed, Jul 14, 2010 at 19:22, Benji York 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 the clients 'know' about them
> to
On Wed, Jul 14, 2010 at 19:22, Benji York wrote:
> [...]
>
> Let me make sure I understand your setup: you have a TemporaryStorage
> running on a central server that is exposed via ZEO to clients. Right?
>
> So, when the ZEO server restarts the temp storage is reset (it's
> contents don't survive
On Sun, Jul 11, 2010 at 1:41 AM, Sebastian Tiedtke wrote:
> We're working on a large scale Plone deployment and recently came across
> some odd behavior with tempstorage at our ZEO server.
> The system setup consists of a central ZEO server that provides the
> storage for content as well as a tem
Hi all,
We're working on a large scale Plone deployment and recently came across
some odd behavior with tempstorage at our ZEO server. A limited number, yet
highly frequented, of pages on our Plone site query backend web services
that provide location based services such as geocoding and routing (
