🌐KR
This document describes how to use Transfer, Response, and Context blocks.
▶ Plan Control
- The access rights to Operator > Async Block are controlled by your subcribe plan.
- If you use an Async Block that does not include a fee, a caution message will appear when saving. (
There are unavailable blocks included. Please check and try again.)
|
Free |
Starter |
Plus |
Pro |
Enterprise |
| **Protocol |
|
|
|
|
|
- Async** | - | - | - | ✓ | ✓ |
▶ Transfer Blockset
- Transfer blocksets are used by servers (services) to request data requests and commands through specific Protocols or to process responses.
| Function |
Explanation |
| ID |
The unique ID of the Transfer blockset is automatically created when the block is registered. |
| protocol unit |
Enter the protocol blockset of the API to be called. |
| contexts |
Define the response object to be received after executing the API as a Response Context block. |
▶ Async
- This is an Adapter Block for Async processing.
- SyncTree is based on the ‘synchronous processing’ method, which is performed step by step from the top.
- Asynchronous processing allows you to efficiently utilize resources to complete requests faster.
| Synchronous |
Asynchronous |
| - Do one task at a time. |
|
- The order of execution is clear, so it is easy to predict the flow. | - Fast processing speed by performing multiple tasks at the same time.
- It is difficult to predict flow or debug because it cannot be guaranteed which will be completed first. |