Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision |
| data_core:tcp [2022/04/18 10:51] – su | data_core:tcp [2022/04/18 10:51] – [Fire & Forget] su |
|---|
| |
| ===== Fire & Forget ===== | ===== Fire & Forget ===== |
| |
| The TCP Event Sink can be configured with "Check Reponse" property set to false for a "Fire & Forget" scenario. | |
| |
| The above "Resilient Data Transfer" method using TCP and MSMQ is not expected to introduce any overhead, however if faster flow was requried, paralel TCP components can be chained directly and configured to "fire-and-forget" by setting the "Check Reponse" property to false. Each event will pass through both fast and resilient flows and are consolidated at their final Alarm Analysis destination. | The above "Resilient Data Transfer" method using TCP and MSMQ is not expected to introduce any overhead, however if faster flow was requried, paralel TCP components can be chained directly and configured to "fire-and-forget" by setting the "Check Reponse" property to false. Each event will pass through both fast and resilient flows and are consolidated at their final Alarm Analysis destination. |
