This is the summary for test reports received on the
zope-tests list between 2011-06-14 00:00:00 UTC and 2011-06-15 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/
On 15 June 2011 19:05, Baiju M wrote:
> On Wed, Jun 15, 2011 at 11:07 PM, Hanno Schlichting wrote:
>> On Wed, Jun 15, 2011 at 7:26 PM, Baiju M wrote:
>>> Is memcached a reliable storage for session data ?
>>>
>>> I would like to hear others experience with memcached
>>> as a reliable storage for
On Wed, Jun 15, 2011 at 11:07 PM, Hanno Schlichting wrote:
> On Wed, Jun 15, 2011 at 7:26 PM, Baiju M wrote:
>> Is memcached a reliable storage for session data ?
>>
>> I would like to hear others experience with memcached
>> as a reliable storage for session data.
>
> It depends on what kind of
On 6/15/11 10:01 AM, Martin Aspeli wrote:
> Hi,
>
> You can use collective.beaker to manage your sessions with beaker, and
> store on the filesystem (if all on the same server) or memcached (if
> on different servers). That's a code change, though.
Products.BeakerSessionDataManager uses collective.
On Wed, Jun 15, 2011 at 7:26 PM, Baiju M wrote:
> Is memcached a reliable storage for session data ?
>
> I would like to hear others experience with memcached
> as a reliable storage for session data.
It depends on what kind of reliability you need. Generally your
sessions should be short-lived a
On 06/15/2011 07:19 PM, Hanno Schlichting wrote:
> On Wed, Jun 15, 2011 at 6:50 PM, Subish K S wrote:
>> We have 10+ Zope (version 2.7) servers ( on different machines). Right now
>> each Zope server independently handles session management which means that
>> if a Zope server fails the users o
On Wed, Jun 15, 2011 at 10:49 PM, Hanno Schlichting wrote:
[...snip...]
> Zope 2's built-in session machinery should handle a
> couple dozen sessions at a time. Once you go beyond that look at
> Beaker (via collective.beaker) and memcached as a backend.
Is memcached a reliable storage for session
On Wed, Jun 15, 2011 at 6:50 PM, Subish K S wrote:
> We have 10+ Zope (version 2.7) servers ( on different machines). Right now
> each Zope server independently handles session management which means that if
> a Zope server fails the users on that Zope server do not get redirected to a
> funct
Hi,
You can use collective.beaker to manage your sessions with beaker, and
store on the filesystem (if all on the same server) or memcached (if
on different servers). That's a code change, though.
Martin
On 15 June 2011 17:50, Subish K S wrote:
> Hi,
>
> We have 10+ Zope (version 2.7) servers
Hi,
We have 10+ Zope (version 2.7) servers ( on different machines). Right now
each Zope server independently handles session management which means that if a
Zope server fails the users on that Zope server do not get redirected to a
functioning Zope server but get "stuck" on the failed Zope
10 matches
Mail list logo