On 1 Jul 2005, at 04:58, Fred Drake wrote:
Since using an additional configuration file is possible (and quite
easy in Zope 2, since the location of the instance is so easy to
discern, I'm not convinced it's actually important to support
embedding the configuration for 3rd-party components into zope.conf.
If you want something you can use now, using a product-specific
configuration file, with an appropriate schema, will do quite well.
It also doesn't require hacking (or monkey-patching) Zope or ZConfig,
so it would be easy to deploy in a variety of situations.

That just has the disadvantage that you're increasing the number of configuration files to maintain in an instance. If it's imported and used in zope.conf at leaast there's just one file to deal with...


Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

Reply via email to