Personal tools
Skip to content. | Skip to navigation
This package provides the WSGIPublisherApplication class which exposes the object publishing machinery in zope.publisher as a WSGI application. It also lets us bring up the Zope application server (parsing zope.conf and site.zcml) with a mere function call: >>> db = zope.app.wsgi.config('zope.conf') This is especially useful for debugging. To bring up Zope and obtain the WSGI application object at the same time, use the getWSGIApplication function. This package also provides an easy to use application factory for PasteDeploy. You can simply specify an application configuration like this in your Paste configuration file: [app:main] use = egg:zope.app.wsgi config_file = s/zope.conf Look for more documentation inside the package itself.
zope.app.zapi
Zope application server ZCML files
This package provides the ZODB schema update generations for all components included in the classic Zope 3 releases.
zope.app.zptpage
Zope applicationcontrol
Definition of authentication basics for the Zope Framework
BForests are dictionary-like objects that use multiple BTrees for a backend and support rotation of the composite trees. This supports various implementations of timed member expirations, enabling caches and semi-persistent storage. A useful and simple subclass would be to promote a key-value pair to the first (newest) bucket whenever the key is accessed, for instance. It also is useful with disabling the rotation capability. Like btrees, bforests come in four flavors: Integer-Integer (IIBForest), Integer-Object (IOBForest), Object-Integer (OIBForest), and Object-Object (OOBForest). The examples here will deal with them in the abstract: we will create classes from the imaginary and representative BForest class, and generate keys from KeyGenerator and values from ValueGenerator. From the examples you should be able to extrapolate usage of all four types.
This package defines a marker interface, zope.broken.IBroken, used to identify objects which cannot be correctly loaded from the ZODB, typically because the class named in their pickle is not importable. The package exists as a dependency inversion, preventing packages which need to use this interface (e.g., zope.container) from inheriting the dependencies of zope.app.broken (where the interface used to be defined).
This package provides shared browser components for the Zope Toolkit.