ZEO cache fails in an ugly manner for small sizes

[Christian Theune]

Part 1: The cache can not be disabled (for testing purposes) by specifying 0 as the size.

Part 2: All sizes that are too small to store the header will cause an unintuitive error.

I'd like to change it so that:

0 disables the cache

other values that are smaller than the header are rejected with an explicit error message.

[Jim Fulton (jim-zope)]

+1.

I read this to address only creating the cache. You are not
addressing adding objects that are too big to fit in the cache.

Jim

On Jan 18, 2008, at 10:51 AM, Christian Theune wrote:

> Public bug reported:
>
> Part 1: The cache can not be disabled (for testing purposes) by
> specifying 0 as the size.
>
> Part 2: All sizes that are too small to store the header will cause an
> unintuitive error.
>
> I'd like to change it so that:
>
> 0 disables the cache
>
> other values that are smaller than the header are rejected with an
> explicit error message.
>
> ** Affects: zodb
> Importance: Undecided
> Status: New
>
> --
> ZEO cache fails in an ugly manner for small sizes
> https://bugs.launchpad.net/bugs/184057
> You received this bug notification because you are a member of Zodb-
> developers, which is the registrant for ZODB.

--
Jim Fulton
Zope Corporation

[Christian Theune (ctheune)]

> +1.
>
> I read this to address only creating the cache. You are not
> addressing adding objects that are too big to fit in the cache.

Yup.

[Christian Theune (ctheune)]

I'll handle this now.

[Christian Theune (ctheune)]

Fixed in r86166.