Skip to content
Integration package for zc.async allowing asynchronous operations in Plone
Python
Find file
Latest commit 9a2146b Feb 25, 2016 nathan.vangheem committed with jensens add classifiers
Failed to load latest commit information.
docs
src/plone pre release & rst Oct 9, 2012
.gitignore add classifiers Apr 25, 2016
MANIFEST.in buildouts refresh Sep 25, 2012
README.rst forgot contents... Oct 9, 2012
base.cfg
bootstrap.py Upload plone.app.async to plone's svn Oct 25, 2010
buildout-plone3-multi-db.cfg Bump zc.async version. Jul 21, 2011
buildout-plone3-single-db.cfg Bump zc.async version. Jul 21, 2011
multidb-base.cfg buildouts refresh Sep 25, 2012
multidb-test-4.0.x.cfg buildout.plonetest is now on github Oct 18, 2012
multidb-test-4.1.x.cfg buildout.plonetest is now on github Oct 18, 2012
multidb-test-4.2.x.cfg buildout.plonetest is now on github Oct 18, 2012
multidb-test-4.3.x.cfg buildout.plonetest is now on github Oct 18, 2012
multidb.cfg buildout.plonetest is now on github Oct 18, 2012
setup.py add classifiers Apr 25, 2016
singledb-base.cfg add parameters for ports for a better thirdparty reuse of the buildouts Sep 25, 2012
singledb-test-4.0.x.cfg
singledb-test-4.1.x.cfg buildout.plonetest is now on github Oct 18, 2012
singledb-test-4.2.x.cfg buildout.plonetest is now on github Oct 18, 2012
singledb-test-4.3.x.cfg buildout.plonetest is now on github Oct 18, 2012
singledb.cfg buildout.plonetest is now on github Oct 18, 2012

README.rst

plone.app.async

Introduction

Integration package for zc.async allowing asynchronous operations in Plone 3 and 4.

Repository

Installation

You will typically run plone.app.async in a ZEO environment, where you will have one or more worker instances carrying out jobs queued by your main zope instances.

For the sake of simplicity it is assumed that you have one instance that can queue new jobs, and one worker instance that consumes them, both operating on a single database. In this case your buildout configuration will look similar to the following:

[zeo]
recipe = plone.recipe.zope2zeoserver
file-storage = ${buildout:directory}/var/filestorage/Data.fs

[instance]
recipe = plone.recipe.zope2instance
eggs = Plone plone.app.async
zcml =
zcml-additional =
    <include package="plone.app.async" file="single_db_instance.zcml" />
environment-vars =
    ZC_ASYNC_UUID ${buildout:directory}/var/instance-uuid.txt

[worker]
recipe = plone.recipe.zope2instance
eggs = ${instance:eggs}
zcml = ${instance:zcml}
zcml-additional =
    <include package="plone.app.async" file="single_db_worker.zcml" />
environment-vars =
    ZC_ASYNC_UUID ${buildout:directory}/var/worker-uuid.txt

There are two important stanzas here:

  • Each instance has to set the ZC_ASYNC_UUID environment variable in order to integrate properly with zc.async.
  • Each instance loads the single_db_instance.zcml configuration. The worker instance loads the single_db_worker.zcml configuration in order to setup the queue and configure itself as a dispatcher.

For more details please look at the example buildout configurations included in the package.

Plone 3

Use zope.app.keyreference

Plone 4

Use five.intid

Credits

Code from Enfold's plone.async.core package has been used for setting up the queues.

References

Something went wrong with that request. Please try again.