zeo-client-name is useless

[Chris McDonough]

The top-level config file key "zeo-client-name" is apparently useless, replaced by a "client" key in the <zeoclient> section of a storage definition. References to "zeo-client-name" in startup code, docs and in the default config file need to be removed.

[Andreas Jung (ajung)]

Can you fix it? :-)

[Tim Peters (tim-one)]

FYI, zeo-client-name appears nowhere in the ZODB or ZEO code, or docs, or component.xml files, in any of the 3.1, 3.2, or 3.3 ZODB/ZEO lines.

The only places I find it are in Zope's zope.conf.in and zopeschema.xml, plus random references on the web (google).

If people are actually using this (I can't tell <sigh>), perhaps it would be better to "make it mean something" (again?)? AFAICT, zeo-client-name has always been in zopeschema.xml.

Hmm ... OK, Zope's handler for zeo-client-name sets the ZEO_CLIENT envar. But ZEO stopped looking at ZEO_CLIENT in ZODB 3.2a1 (and also stopped looking at CLIENT_HOME and INSTANCE_HOME).

Eek! AFAICT also, nothing looks at stuff like database-quota-size or the ZOPE_DATABASE_QUOTA envar it sets.

For that matter, I can't find any actual use of automatically-quote-dtml-request-data (after tracing its one apparent use to a dead end) ... I'm missing something, or there's a lot of write-only nonsense in zope.conf.