Hi Tim,
Tim Peters wrote at 2005-6-29 16:46 -0400:
>I don't hate the feature, but I hate that it's undocumented, and I hate that
>it's untested. I particularly hate that the ClientStorage constructor has
>17 arguments now, and that the docs for its `name` and `storage` arguments
>are incomprehens
Jeremy Hylton wrote at 2005-6-29 15:31 -0400:
> ...
>The benefit is that you get to run
>several storages using a single ZEO server process and TCP port. It's
>probably not a good idea to use a single process for many servers,
>although it might be convenient to use a single port.
Maybe, I can pr
On Wed, 2005-06-29 at 16:46 -0400, Tim Peters wrote:
> [Chris McDonough]
> > I also use this feature but I would be happy to stop using it if it made
> > the code materially simpler to maintain.
>
> I don't hate the feature, but I hate that it's undocumented, and I hate that
> it's untested. I pa
[Chris McDonough]
> I also use this feature but I would be happy to stop using it if it made
> the code materially simpler to maintain.
I don't hate the feature, but I hate that it's undocumented, and I hate that
it's untested. I particularly hate that the ClientStorage constructor has
17 argumen
Chris McDonough wrote:
I also use this feature but I would be happy to stop using it if it made
the code materially simpler to maintain.
+1
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
CTO (540) 361-1714http://www.python.org
Zope Corp
I also use this feature but I would be happy to stop using it if it made
the code materially simpler to maintain.
- C
On Wed, 2005-06-29 at 15:31 -0400, Jeremy Hylton wrote:
> On 6/29/05, Tim Peters <[EMAIL PROTECTED]> wrote:
> > [Tim Peters]
> > >>
> > >> As before, I'd run a different ZEO
On 6/29/05, Tim Peters <[EMAIL PROTECTED]> wrote:
> [Tim Peters]
> >>
> >> 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).
>
> [Dieter
[Tim Peters]
>>
>> 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).
[Dieter Maurer]
> I do not know whether it is supported but it works in
Tim Peters wrote at 2005-6-28 17:09 -0400:
>
>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).
I do not know whether it is supported but it wo
[Tim Peters]
>> 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).
[Lukas Linhart]
> Well, I'm stuck on zodb 3.2.x line because I'm using IndexedC
> 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
14 matches
Mail list logo