Overview

This section describes the recommended daemon loop for implementing the reverse invoke protocol.

The loop coordinates communication between the daemon and Talk2Sync. It determines whether Talk2Sync is requesting new information from the external system or waiting for the daemon to write information into the legacy application.

After the current operation is completed, the daemon should wait for a defined period before starting the loop again.

Some steps in the flow are clickable and provide additional details about the substructure or procedure represented by that step.

Daemon Loop

Loop Sequence

The daemon follows this sequence:

1. Start the reverse invoke loop.
2. Check whether Talk2Sync is asking to fetch information.
3. If requested, push upstream products.
4. If requested, push upstream orders.
5. Check whether Talk2Sync is asking to pull information.
6. If requested, pull down products.
7. If requested, pull down orders.
8. Sleep for the configured period.
9. Start the loop again.

If Talk2Sync is not requesting an operation at either decision point, the daemon proceeds to the next stage without performing that operation.

Next Steps

• Review Product Upload for the upstream product synchronization flow.
• Review Order Upload for the upstream order synchronization flow.
• Review Product Download for the product download flow.
• Review Order Download for the order download flow.
• Review Sleep for the daemon wait state.