 Celery 2.5 DocumentationFlask flask-celery web2py web2py-celery 1.1.2 Overview This is a high level overview of the architecture. The broker delivers tasks to the worker nodes. A worker node is a networked machine running replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and it comes with three implementations: • inotify (Linux) Used if the pyinotify library is installed replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and Celery comes with three implementations: • inotify (Linux) Used if the pyinotify library0 码力 | 400 页 | 1.40 MB | 1 年前3 Celery 2.5 DocumentationFlask flask-celery web2py web2py-celery 1.1.2 Overview This is a high level overview of the architecture. The broker delivers tasks to the worker nodes. A worker node is a networked machine running replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and it comes with three implementations: • inotify (Linux) Used if the pyinotify library is installed replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and Celery comes with three implementations: • inotify (Linux) Used if the pyinotify library0 码力 | 400 页 | 1.40 MB | 1 年前3
 Celery 2.5 Documentationcelery-pylons Flask flask-celery web2py web2py-celery Overview This is a high level overview of the architecture. http://cloud.github.com/downloads/celery/celery/Celery-Overview-v4.jpg The broker delivers replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and it comes with three implementations: inotify (Linux) Used if the pyinotify library is installed replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and Celery comes with three implementations: inotify (Linux) Used if the pyinotify library is0 码力 | 647 页 | 1011.88 KB | 1 年前3 Celery 2.5 Documentationcelery-pylons Flask flask-celery web2py web2py-celery Overview This is a high level overview of the architecture. http://cloud.github.com/downloads/celery/celery/Celery-Overview-v4.jpg The broker delivers replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and it comes with three implementations: inotify (Linux) Used if the pyinotify library is installed replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and Celery comes with three implementations: inotify (Linux) Used if the pyinotify library is0 码力 | 647 页 | 1011.88 KB | 1 年前3
 Celery 3.1 Documentationreplaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and it comes with three implementations: • inotify (Linux) Used if the pyinotify library is installed replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and Celery comes with three implementations: • inotify (Linux) Used if the pyinotify library0 码力 | 607 页 | 2.27 MB | 1 年前3 Celery 3.1 Documentationreplaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and it comes with three implementations: • inotify (Linux) Used if the pyinotify library is installed replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and Celery comes with three implementations: • inotify (Linux) Used if the pyinotify library0 码力 | 607 页 | 2.27 MB | 1 年前3
 Celery 3.1 Documentationreplaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and it comes with three implementations: inotify (Linux) Used if the pyinotify library is installed replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and Celery comes with three implementations: inotify (Linux) Used if the pyinotify library is0 码力 | 887 页 | 1.22 MB | 1 年前3 Celery 3.1 Documentationreplaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and it comes with three implementations: inotify (Linux) Used if the pyinotify library is installed replaced by fresh processes effectively reloading the code. File system notification backends are pluggable, and Celery comes with three implementations: inotify (Linux) Used if the pyinotify library is0 码力 | 887 页 | 1.22 MB | 1 年前3
 Celery 1.0 Documentationfor Redis and databases is also available. 1.1.1 Overview This is a high level overview of the architecture. The broker pushes tasks to the worker servers. A worker server is a networked machine running0 码力 | 123 页 | 400.69 KB | 1 年前3 Celery 1.0 Documentationfor Redis and databases is also available. 1.1.1 Overview This is a high level overview of the architecture. The broker pushes tasks to the worker servers. A worker server is a networked machine running0 码力 | 123 页 | 400.69 KB | 1 年前3
 Celery 1.0 Documentationsupport for Redis and databases is also available. Overview This is a high level overview of the architecture. http://cloud.github.com/downloads/ask/celery/Celery-Overview-v4.jpg The broker pushes tasks0 码力 | 221 页 | 283.64 KB | 1 年前3 Celery 1.0 Documentationsupport for Redis and databases is also available. Overview This is a high level overview of the architecture. http://cloud.github.com/downloads/ask/celery/Celery-Overview-v4.jpg The broker pushes tasks0 码力 | 221 页 | 283.64 KB | 1 年前3
 Celery 2.0 DocumentationCelery Documentation, Release 2.0.3 (stable) 1.1.1 Overview This is a high level overview of the architecture. The broker pushes tasks to the worker servers. A worker server is a networked machine running0 码力 | 165 页 | 492.43 KB | 1 年前3 Celery 2.0 DocumentationCelery Documentation, Release 2.0.3 (stable) 1.1.1 Overview This is a high level overview of the architecture. The broker pushes tasks to the worker servers. A worker server is a networked machine running0 码力 | 165 页 | 492.43 KB | 1 年前3
 Celery 2.0 Documentationinstalling from source Using the development version Overview This is a high level overview of the architecture. http://cloud.github.com/downloads/ask/celery/Celery-Overview-v4.jpg The broker pushes tasks0 码力 | 284 页 | 332.71 KB | 1 年前3 Celery 2.0 Documentationinstalling from source Using the development version Overview This is a high level overview of the architecture. http://cloud.github.com/downloads/ask/celery/Celery-Overview-v4.jpg The broker pushes tasks0 码力 | 284 页 | 332.71 KB | 1 年前3
 Celery 2.1 Documentation3 Celery Documentation, Release 2.1.4 1.1.1 Overview This is a high level overview of the architecture. The broker delivers tasks to the worker servers. A worker server is a networked machine running0 码力 | 285 页 | 1.19 MB | 1 年前3 Celery 2.1 Documentation3 Celery Documentation, Release 2.1.4 1.1.1 Overview This is a high level overview of the architecture. The broker delivers tasks to the worker servers. A worker server is a networked machine running0 码力 | 285 页 | 1.19 MB | 1 年前3
 Celery 2.1 Documentationinstalling from source Using the development version Overview This is a high level overview of the architecture. http://cloud.github.com/downloads/ask/celery/Celery-Overview-v4.jpg The broker delivers tasks0 码力 | 463 页 | 861.69 KB | 1 年前3 Celery 2.1 Documentationinstalling from source Using the development version Overview This is a high level overview of the architecture. http://cloud.github.com/downloads/ask/celery/Celery-Overview-v4.jpg The broker delivers tasks0 码力 | 463 页 | 861.69 KB | 1 年前3
共 22 条
- 1
- 2
- 3














