Hi Darryl,
On Wed, Oct 12, 2011, Darryl Dixon - Winterhouse Consulting
wrote:
> [...snip...]
> In essence, [to have one database per web site is] exactly the same
> - just that everywhere that you would normally use a
> section in your zope.conf you instead use a section.
> [...snip...]
Than
Hello,
According to source code comments, a demo storage will support blobs
if the underlying storage does. But I find that it's impossible to
wrap a in a demo storage and have it working.
Am I doing something wrong – or, if it's not supported, would it be
difficult to do so and is anyone intere
Hi Dylan,
On Wed, Oct 12, 2011, Dylan Jay wrote:
> It looks a bit like this if you are using zope2instance recipe in buildout
>
> zope-conf-additional +=
> %import relstorage
>
>
> mount-point /www/mnt
> cache-size 5000
>
> blob-dir ${buildo
Hi,
Memcached allows to specify a variety of timeouts in its "behaviors", in
particular there are connect_timeout, send_timeout and receive_timeout. [1]
Since we recently had to customize relstorage.pylibmc_wrapper.Client to
accommodate the timeout values, I was wondering if it made sense to ma
On Oct 17, 2011, at 5:52 AM, Malthe Borch wrote:
> According to source code comments, a demo storage will support blobs
> if the underlying storage does. But I find that it's impossible to
> wrap a in a demo storage and have it working.
>
> Am I doing something wrong
Since you did not explain
On Mon, Oct 17, 2011 at 5:52 AM, Malthe Borch wrote:
> Hello,
>
> According to source code comments, a demo storage will support blobs
> if the underlying storage does. But I find that it's impossible to
> wrap a in a demo storage and have it working.
>
> Am I doing something wrong – or, if it's
Sorry for the confusion
It is a buildout feature to make your variable substitutions which is
what Ive done there.
Replicas are for redundant MySQL servers. I doubt you need that. Just
check the relstorage docs to see what options you need.
Dylan Jay
Technical solution manager
PretaWeb 99552830
