Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:rule:event_gateway_warning [2023-09-10 12:51] – [Use the event gateway with caution] Anatoly Belaychuk | en:rule:event_gateway_warning [2024-08-24 15:49] (current) – [Use event gateways with caution] Anatoly Belaychuk | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Use the event gateway | + | ====== Use event gateways |
- | {{tag>subprocess | + | {{tag> |
+ | |||
+ | Event gateway immediately interrupts all catching events when any single one occurs. | ||
+ | For more versatile logic consider the combination of parallel gateway and terminating event. | ||
- | Mind the difference between the diagrams above: while the "to do" process waits for the message all the time till the end, the "no to do" process interrupts when the timer triggers. If the message arrives while while we are discussing the issue with the client, it won't be catched and the process will hang after returning to the event gateway. This is rather common mistake. | ||
===== ✔ How to ===== | ===== ✔ How to ===== | ||
Line 305: | Line 307: | ||
===== Notes ===== | ===== Notes ===== | ||
- | Mind the difference between the diagrams | + | Mind the difference between the diagrams |
- | ===== Exceptions ===== | + | |
- | + | ||
- | Specify exceptions to the rule above, if any | + | |
===== See also ===== | ===== See also ===== | ||
- | Reference similar rules here (this section is optional) | + | * [[en: |
+ | ===== Автор(ы) ===== | ||
- | ===== Автор(ы) ===== | + | --- // |
- | Put signature here |