معرفی شرکت ها
collective.taskqueue-1.0
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشترتوضیحات
Asyncore-based asynchronous task queue for Plone
| ویژگی | مقدار |
|---|---|
| سیستم عامل | - |
| نام فایل | collective.taskqueue-1.0 |
| نام | collective.taskqueue |
| نسخه کتابخانه | 1.0 |
| نگهدارنده | [] |
| ایمیل نگهدارنده | [] |
| نویسنده | Asko Soukka |
| ایمیل نویسنده | asko.soukka@iki.fi |
| آدرس صفحه اصلی | https://github.com/collective/collective.taskqueue/ |
| آدرس اینترنتی | https://pypi.org/project/collective.taskqueue/ |
| مجوز | GPL |
collective.taskqueue
====================
.. image:: https://secure.travis-ci.org/collective/collective.taskqueue.png
:target: http://travis-ci.org/collective/collective.taskqueue
*collective.taskqueue* enables asynchronous tasks in Plone add-ons by
providing a small framework for asynchronously queueing requests to
ZPublisher. With this approach, asynchronous tasks
are just normal calls to normally registered browser views (or other
traversable callables) and they are authenticated using PAS as are all the other
requests.
In addition, it's possible to configure views so that they are visible only for
asynchronous requests. Also, *collective.taskqueue* ships with a special
PAS-plugin, which authenticates each request as the user who queued it.
Minimal configuration:
.. code:: ini
zope-conf-additional =
%import collective.taskqueue
<taskqueue />
<taskqueue-server />
Minimal configuration gives you one volatile instance-local queue and
consumer, but no guarantee on delivery.
Minimal configuration with multiple queues:
.. code:: ini
zope-conf-additional =
%import collective.taskqueue
<taskqueue />
<taskqueue-server />
<taskqueue>
queue mailhost
</taskqueue>
<taskqueue-server>
queue mailhost
</taskqueue-server>
Preferred minimal configration with Redis:
.. code:: ini
eggs =
collective.taskqueue [redis]
zope-conf-additional =
%import collective.taskqueue
<taskqueue>
type redis
unix_socket_path ${buildout:directory}/var/redis.sock
</taskqueue>
<taskqueue-server>
name ${:_buildout_section_name_}
</taskqueue-server>
Redis-support gives you distributable queues, which can be shared between
instances. All instances should have queue-specific `<taskqueue />`, but only
the consuming instance requires `<taskqueue-server />`.
Example Redis configuration with multiple queues:
.. code:: ini
eggs =
collective.taskqueue [redis]
zope-conf-additional =
%import collective.taskqueue
<taskqueue>
type redis
unix_socket_path ${buildout:directory}/var/redis.sock
</taskqueue>
<taskqueue-server>
name ${:_buildout_section_name_}
</taskqueue-server>
<taskqueue>
type redis
queue mailhost
unix_socket_path ${buildout:directory}/var/redis.sock
</taskqueue>
<taskqueue-server>
queue mailhost
name ${:_buildout_section_name_}
</taskqueue-server>
It's recommended to only use local Redis-installations, because remote
connections can be killed by firewalls (there's no ping or heartbeat to keep
the connection alive through enterprise firewalls).
Queue a task:
.. code:: python
from collective.taskqueue import taskqueue
task_id = taskqueue.add('/Plone/path/to/my/view')
Tasks are queued (and consumed) after a successful transaction.
To make views visible only for asynchronous requests, views can be registered
for a special layer ``collective.taskqueue.interfaces.ITaskQueueLayer``, which
is only found from requests dispatched by *collective.taskqueue*.
By default, ``taskqueue.add`` copies headers from the current requests to the
asynchronous request. That should be enough to authenticate the requests in
exactly the the same way as the current request was authenticated.
``taskqueue.add`` returns uuid like id for the task, which can be used e.g. to
track the task status later. Task id later provided as ``X-Task-Id`` header in
the queued request. You can get it in your task view with ``self.request.getHeader('X-Task-Id')``.
More robust authentication can be implemented with a custom PAS-plugin.
*collective.taskqueue* ships with an optionally installable PAS-plugin, which
authenticates each request as the user who queued it. To achieve this,
*collective.taskqueue* appends ``X-Task-User-Id``-header into the queued
request.
Taskqueue API has been inspired by `Google AppEngine Task Queue API`__.
__ https://developers.google.com/appengine/docs/python/taskqueue/
Introspecting queues
--------------------
As a minimalistic asynchronous framework for Plone, *collective.taskqueue*
does not provider any user interface for observing or introspecting queues.
Yet, from trusted Python, it is possible to look up a current length of
a named queue (name of the default queue is "default"):
.. code:: python
from zope.component import getUtility
from collective.taskqueue.interfaces import ITaskQueue
len(getUtility(ITaskQueue, name='default'))
Advanced configuration
----------------------
Supported ``<taskqueue />``-settings are:
``queue`` *(default=default)*
Unique task queue name.
``type`` *(default=local)*
Task queue type ('local' or 'redis') or full class path to
a custom type.
``unix_socket_path``
Redis server unix socket path (use instead of *host* and *port*).
Other supported Redis-queue options are: *host*, *port*, *db* and *password*.
Supported ``<taskqueue-server />``-settings are:
``name`` *(default=default)*
Consumer name, preferably instance name. Consumer is name used by
Redis-queues for reserving messages from queue to achieve quaranteed
delivery.
``queue`` *(default=default)*
Queue name for this consumer (consuming server). There must be a
``<taskqueue/>`` with matching *queue*-value registered.
``concurrent_limit`` *(default=1)*
Maximum concurrent task limit for this consumer. It's recommend to
set this smaller than *zserver-thread*-count. Leaving this to the
default (``1``) should give the best results in terms of minimal
ConflictErrors.
``retry_max_count`` *(default=10)*
Maximum ZPublisher retry count for requests dispatched by this
consumer.
.. note:: Once this limit has been exceeded by ZPublisher, the conflicting
task is permanently trashed. (An alternative behavior is possible
by implementing a custom queue class.)
Advanced usage
--------------
``taskqueue.add`` accepts the following arguments (with *default* value):
``url`` *(required, no default)*
Target path representing the task to be called.
``method`` *(optional, default=GET)*
HTTP-method for the call. Must be either *GET* or *POST*.
``params`` *(optional, default=None)*
A dictionary of optional task arguments, which are appended as query string
after the given *url*.
``headers`` *(optional, default=None)*
A dictionary of optional HTTP-headers to be appended to (or used to replace)
the headers copied from the active request.
``payload`` *(optional, default=current)*
An optional payload for *POST*-request. Payload from the active request
will be copied by default. Copying the active payload can be prevented
with *payload=None*.
``queue`` *(optional, default=alphabetically-first-registered-queue)*
An optional queue name, when more than one queue is registered.
How Redis queueing works
------------------------
1. ``taskqueue.add`` prepares a message, which will be pushed (``lpush``)
into key ``collective.taskqueue.%(queue)s`` (where ``%(queue)s`` is the
name of the queue) at the end of the transaction. If Redis connection is
down during the transaction vote, the whole transaction is aborted.
2. ``<taskqueue-server />`` reads each message (``rpoplpush``) from queue so
that they will remain in key ``collective.taskqueue.%(queue)s.%(name)s``
(where ``%(name)s`` is the name of the ``<taskqueue-server/>``) until
each asynchronous processing request has returned a HTTP response.
3. On startup, and when all known messages have been processed,
``<taskqueue-server/>`` purges ``collective.taskqueue.%(queue)s.%(name)s``
into ``collective.taskqueue.%(queue)s`` (with ``rpoplpush``) and
those tasks are processed again. (E.g. if Plone was forced to restart
in middle of task handling request.)
Redis integration uses PubSub to notify itself about new messages in queue
(and get as instant handling as possible in terms of Plone's asyncore-loop).
Changelog
=========
1.0 (2020-02-10)
----------------
- Add support for Plone 5.2
[gforcada]
- Fix to use @implementer decorator
[petschki]
0.8.2 (2017-01-03)
------------------
- Fix issue where got bool header value caused error on task creationg
[datakurre]
0.8.1 (2017-01-02)
------------------
- Fix issue where task queue request with method POST created from GET method
failed because of empty payload in the original request
[datakurre]
0.8.0 (2015-12-13)
------------------
- Add support for Plone 5
[datakurre]
- Fix issue where additional params could not be appended for url with query string
[datakurre]
0.7.1 (2015-01-26)
------------------
- Fix problems with conflicting transactions: only enqueue tasks when
transaction is successfully finished.
[jone]
0.7.0 (2014-12-29)
------------------
- Replace NoRollbackSavepoint with rollback 'supporting' DummySavepoint
[datakurre]
0.6.2 (2014-12-19)
------------------
- Add minimal savepoint-support with NoRollbackSavepoint
[datakurre]
0.6.1 (2014-08-05)
------------------
- Fix issue where language bindings are not set for task queue requests,
because the request is not HTTPRequest, but only inherits it
[datakurre]
0.6.0 (2014-05-19)
------------------
- Add taskqueue.add to return task id, which later matches
request.getHeader('X-Task-Id')
[datakurre]
0.5.1 (2014-05-14)
------------------
- Fix issue where concurrent task counter mutex was not released due to
uncaught exception
[datakurre]
- Fix issue where a socket in asyncore.map was closed during asyncore.poll
[datakurre]
0.5.0 (2014-04-03)
------------------
- Fix threading and execution order related issue where currently active
Redis tasks were requeued (and processed more than once)
[datakurre]
- Add 'X-Task-Id'-header to help keeping track of tasks n consuming views
[datakurre]
0.4.4 (2013-11-25)
------------------
- Fix regression where redis+msgpack where accidentally always required [#7]
[datakurre]
- Update docs
[Dylan Jay]
- Fix default for 'unix_socket_path' [fixes #8]
[Dylan Jay]
0.4.3 (2013-11-15)
------------------
- Update README
[datakurre]
0.4.2 (2013-11-15)
------------------
- Updated README
[datakurre]
0.4.1 (2013-11-14)
------------------
- Updated README
[datakurre]
0.4.0 (2013-11-14)
------------------
- Refactor configuration by replacing explicit utilities and
<product-configuration/> with <taskqueue/>-component
[datakurre]
0.3.1 (2013-11-13)
------------------
- Enhance acceptance testing support with the first acceptance tests
[datakurre]
0.3.0 (2013-11-10)
------------------
- Fix TaskQueueServer to re-connect to Redis after Redis restart
[datakurre]
- Fix to ping Redis on Zope start only in development mode
[datakurre]
- Add optional Task Queue PAS plugin to independently authenticate
queued tasks as their creator
[datakurre]
0.2.2 (2013-11-09)
------------------
- Fix to flush Redis pub-notifications only when queue has been emptied
to ensure that all messages will be processed
[datakurre]
0.2.1 (2013-11-09)
------------------
- Fix taskqueue socket to be not readable by default
[datakurre]
0.2.0 (2013-11-09)
------------------
- Enhance Redis-integration to connect redis notification pubsub-socket
directly to asyncore on instant message handling
[datakurre]
- Fix to require redis >= 2.4.10 [fixes #2]
[datakurre]
- Fix to not start with clear error when clearly intending to use
RedisTaskQueues without redis-dependencies. Also crash when cannot connect to
Redis. [fixes #1]
[datakurre]
0.1.0 (2013-11-03)
------------------
- First release for experimental use.
نیازمندی
| مقدار | نام |
|---|---|
| - | setuptools |
| - | six |
| - | Zope2 |
| - | five.globalrequest |
| >=2.4.10 | redis |
| - | msgpack-python |
| - | plone.app.testing |
| >=0.7.0rc4 | plone.app.robotframework |
نحوه نصب
نصب پکیج whl collective.taskqueue-1.0:
pip install collective.taskqueue-1.0.whl
نصب پکیج tar.gz collective.taskqueue-1.0:
pip install collective.taskqueue-1.0.tar.gz