> As before, I'd run a different ZEO server for each database. I'm not sure
> that what you're doing here will be supported for much longer (or really
> even _is_ supported anymore -- see my last msg).
Well, I'm stuck on zodb 3.2.x line because I'm using IndexedCatalog.
> > How do I connect to
[Lukas Linhart]
...
> Well I meant: when I'm having ZEO configured this way
> (/etc/zeo/zeo.conf):
>
>
> address localhost:11000
> monitor-address localhost:11001
>
>
>
> path /var/www/databases/zodb/almad-net.fs
>
>
> path /var/www/databases/zodb/zapisnik-test.
Sorry for not posting into mailing list, I'm just used only to press 'r'
key :/
-- Forwarded message --
Hello,
> import ZODB.config
> db = ZODB.config.databaseFromURL('/tmp/zeo.conf')
>
> then works unchanged no matter which storage is specified in /tmp/zeo.conf.
>
> M
[Lukas Linhart]
> sorry for bothering in Dev list, but I've posted this to c.l.p with no
> answer and I don't knew where to ask.
>
> I've rtfm again and I really don't knew :]
>
>
> One nice feature of the configuration file is that you don't need
> to specify imports for a specific storage. That
Tim Peters wrote at 2005-6-27 15:38 -0400:
> ...
[Dieter]
>> Probably, "ZEOClientStorage" (and the ZEO server) should use
>> "SO_KEEPALIVE" to enable TCP keepalive messages. However, the default
>> TCP timeouts are probably too high (2 hours) for many ZODB applications
>> (like ours).
[Tim]
>Secti
Hello,
sorry for bothering in Dev list, but I've posted this to c.l.p with no answer
and I don't knew where to ask.
I've rtfm again and I really don't knew :]
One nice feature of the configuration file is that you don't need to specify
imports for a specific storage. That makes the code a l