Celery 2.3 Documentationbeen received will not be deleted from the broker until it has been acknowledged by the receiver, so if the receiver dies in the middle of processing the message, it will be re-sent at a later point in time Dispatcher(connection=None, hostname=None, enabled=True, channel=None, buffer_while_offline=True) Receiver(connection, handlers=None, routing_key=’#’, node_id=None) State() default_dispatcher(*args, **kwds) ‘{receriverkey (id): weakref(receiver)}‘ mappings. connect(receiver, sender=None, weak=True, dispatch_uid=None) Connect receiver to sender for signal. Parameters • receiver – A function or an instance0 码力 | 334 页 | 1.25 MB | 1 年前3
Celery 2.2 Documentationbeen received will not be deleted from the broker until it has been acknowledged by the receiver, so if the receiver dies in the middle of processing the message, it will be re-sent at a later point in time Dispatcher(connection=None, hostname=None, enabled=True, channel=None, buffer_while_offline=True) Receiver(connection, handlers=None, routing_key=’#’, node_id=None) State() celery.events.create_event(type ‘{receriverkey (id): weakref(receiver)}‘ mappings. connect(receiver, sender=None, weak=True, dispatch_uid=None) Connect receiver to sender for signal. Parameters • receiver – A function or an instance0 码力 | 314 页 | 1.26 MB | 1 年前3
Celery 2.2 Documentationbeen received will not be deleted from the broker until it has been acknowledged by the receiver, so if the receiver dies in the middle of processing the message, it will be re-sent at a later point in time Dispatcher(connection=None, hostname=None, enabled=True, channel=None, buffer_while_offline=True) Receiver(connection, handlers=None, routing_key='#', node_id=None) State() celery.events.create_event(type `{receriverkey (id): weakref(receiver)}` mappings. connect(receiver, sender=None, weak=True, dispatch_uid=None) Connect receiver to sender for signal. Parameters: receiver – A function or an instance0 码力 | 505 页 | 878.66 KB | 1 年前3
Celery 2.0 Documentationsignify that a message has been received and processed successfully. The message is sent to the next receiver if it has not been acknowledged before the client connection is closed. Note the delivery tag listed and celery 67 Celery Documentation, Release 2.0.3 (stable) been acknowledged by the receiver, so if the receiver dies in the middle of processing the message, it will be re-sent at a later point in time ‘‘{receriverkey (id): weakref(receiver)}‘‘ mappings. connect(receiver, sender=None, weak=True, dispatch_uid=None) Connect receiver to sender for signal. Parameters • receiver – A function or an instance0 码力 | 165 页 | 492.43 KB | 1 年前3
Celery 2.3 Documentationbeen received will not be deleted from the broker until it has been acknowledged by the receiver, so if the receiver dies in the middle of processing the message, it will be re-sent at a later point in time Dispatcher(connection=None, hostname=None, enabled=True, channel=None, buffer_while_offline=True) Receiver(connection, handlers=None, routing_key='#', node_id=None) State() default_dispatcher(*args, **kwds) `{receriverkey (id): weakref(receiver)}` mappings. connect(receiver, sender=None, weak=True, dispatch_uid=None) Connect receiver to sender for signal. Parameters: receiver – A function or an instance0 码力 | 530 页 | 900.64 KB | 1 年前3
Celery v5.0.1 Documentationsomething with those events at an interval. For real-time event processing you should use app.events.Receiver directly, like in Real-time processing. Here is an example camera, dumping the snapshot to screen: state = app.events.State() with app.connection() as connection: recv = app.events.Receiver(connection, handlers={'*': state.event}) with DumpCam(state, freq=freq): recv processing To process events in real-time you need the following An event consumer (this is the Receiver) A set of handlers called when events come in. You can have different handlers for each event0 码力 | 2313 页 | 2.13 MB | 1 年前3
Celery v5.0.2 Documentationsomething with those events at an interval. For real-time event processing you should use app.events.Receiver directly, like in Real-time processing. Here is an example camera, dumping the snapshot to screen: state = app.events.State() with app.connection() as connection: recv = app.events.Receiver(connection, handlers={'*': state.event}) with DumpCam(state, freq=freq): recv processing To process events in real-time you need the following An event consumer (this is the Receiver) A set of handlers called when events come in. You can have different handlers for each event0 码力 | 2313 页 | 2.14 MB | 1 年前3
Celery v5.0.0 Documentationsomething with those events at an interval. For real-time event processing you should use app.events.Receiver directly, like in Real-time processing. Here is an example camera, dumping the snapshot to screen: state = app.events.State() with app.connection() as connection: recv = app.events.Receiver(connection, handlers={'*': state.event}) with DumpCam(state, freq=freq): recv processing To process events in real-time you need the following An event consumer (this is the Receiver) A set of handlers called when events come in. You can have different handlers for each event0 码力 | 2309 页 | 2.13 MB | 1 年前3
Celery v5.0.5 Documentationsomething with those events at an interval. For real-time event processing you should use app.events.Receiver directly, like in Real-time processing. Here is an example camera, dumping the snapshot to screen: state = app.events.State() with app.connection() as connection: recv = app.events.Receiver(connection, handlers={'*': state.event}) with DumpCam(state, freq=freq): recv processing To process events in real-time you need the following An event consumer (this is the Receiver) A set of handlers called when events come in. You can have different handlers for each event0 码力 | 2315 页 | 2.14 MB | 1 年前3
Celery 2.0 Documentationsignify that a message has been received and processed successfully. The message is sent to the next receiver if it has not been acknowledged before the client connection is closed. Note the delivery tag been received will not be deleted from the broker until it has been acknowledged by the receiver, so if the receiver dies in the middle of processing the message, it will be re-sent at a later point in time ``{receriverkey (id): weakref(receiver)}`` mappings. connect(receiver, sender=None, weak=True, dispatch_uid=None) Connect receiver to sender for signal. Parameters: receiver – A function or an instance0 码力 | 284 页 | 332.71 KB | 1 年前3
共 216 条
- 1
- 2
- 3
- 4
- 5
- 6
- 22













