Lines Matching full:trigger

112 received message. Each trigger is registered with the ``trigger``
116 becomes available, the progress group will call the trigger with the
122 cases where the trigger's purpose is to immediately reply with a
123 value, the trigger should be registered with the
133 some cases, received "early" by a trigger. These messages are not
150 trigger, that returns the resulting value--a
190       void trigger(int tag, const Handler& handler);
259       void trigger(int tag, const Handler& handler);
261 Registers a trigger with the given process group. The trigger will
274   specified when the trigger was registered.
277   The context in which the trigger is executed. This will be a value of
278   type ``trigger_receive_context``, which stages whether the trigger
284 attaching a distributed data structure. A trigger can be invoked in
286 operation. There is also a `simple trigger interface`_ for defining
296 Like the ``trigger`` method, registers a trigger with the given
297 process group. The trigger will watch for messages with the given
300 normal trigger. However, a trigger registered with
303 trigger. Thus, ``trigger_with_reply`` should only be used for messages
306 ``send_oob_with_reply``. There is also a `simple trigger interface`_
318 what context the currently executing trigger is being invoked.
487 .. _Simple trigger interface: simple_trigger.html