API Call in Typical Scenarios

API Description

Windows SDK APIs are classified into active calling APIs, callback APIs, and message notification APIs.

Active calling APIs: The application actively calls these APIs to complete tasks. For example, the Init API is called for initialization.

Callback APIs: Active API calling and SDK internal task processing are asynchronous. After a task in the SDK is completed, callback APIs are called to notify the application. For example, the OnInitResult API is called to notify the application of the initialization result.

Message notification APIs: These APIs are called by the SDK to notify the application of events triggered by the Huawei Cloud Meeting server or the SDK. For example, the OnConfIncoming API is called to notify the application of meeting calls.

API Call in Typical Scenarios

Figure 1 API call in typical scenarios

1. Generally, the application process needs to be killed before application upgrade. To facilitate upgrade management, you can customize the name of the HwmSdk.exe file in the HwmSdk folder before initialization.

2. Login is not mandatory. You can use the meeting ID and password to join a created meeting without login.

APIs for starting sharing, ending sharing, leaving a meeting, and ending a meeting have been provided on the UI of the SDK. If a third-party application does not need these functions, it does not need to call the corresponding APIs.