Introduction

1. Basic Description

  Polyv Live Streaming is built on the company's years of video technology expertise. Based on professional cross-platform video codec technology and a large-scale video content delivery network, it provides stable, smooth, low-latency, and high-concurrency real-time audio and video services.

  Polyv Seminar Java SDK allows you to easily integrate Polyv live streaming multi-person meeting scenarios without complex programming.

  Polyv Seminar Java SDK is implemented based on the Polyv Seminar API, wrapping and optimizing it to free B-end users from common tasks. It encapsulates and optimizes API call logic and exception handling. B-end users only need to encapsulate request parameters and hand them over to the Polyv Seminar Java SDK for processing. After processing, the SDK returns results, and B-end users continue their business logic based on the returned data. Currently, the Polyv Seminar Java SDK covers most frequently used API operations, including attendee management, channel information management, and playback information management.

  If you encounter any issues while using the Polyv Seminar Java SDK, please contact online customer service to ask after-sales technical support questions. Please submit the runtime environment, operation steps, error feedback information, and contact details together to facilitate quick problem identification and resolution.

2. Overall SDK Design

1. B-end administrators create basic channel information through the SDK, such as channel name, host password, attendee password, and other basic attributes;

2. B-end administrators set basic channel attendance conditions through the SDK;

3. C-end hosts log into the live channel via web pages, live streaming software, or other tools to prepare for the meeting;

4. C-end attendees log into the live channel via web pages, live streaming software, or other tools to join the meeting;

5. After the meeting ends, B-end users perform playback and storage settings, obtain statistical analysis data, and complete the seminar business cycle;

3. Detailed SDK Design

4. SDK Business Logic Analysis

 * Prerequisite: SDK global initialization: Before calling the SDK, global parameters must be configured. Configurable parameters include account information (appId, userId, appSecret) and HTTP connection pool parameters (timeout, maxClientNum). For details, see Initialization

 * SDK global parameter injection: The SDK injects globally configured parameters into the request object;

 * Signature generation: The SDK uses the MD5 algorithm signature rule to generate a signature;

 * Parameter validity check: The SDK uses a custom parameter validation tool to check input parameters. If any parameter is invalid, a PloyvSdkException will be thrown. The exception's message includes the specific field that failed validation. This is a runtime exception and must be caught to handle related business logic;

 * Send HTTP request and obtain returned data: The SDK initializes an HTTP connection pool during initialization. All SDK requests are sent through this connection pool;

 * Parse returned data: If the SDK call succeeds normally, the response object is encapsulated and returned normally. If the server returns an error message, the SDK will throw a PloyvSdkException. The exception's message includes the specific server execution error information. This is a runtime exception and must be caught to handle related business logic;

5. Call Flow Template

  The above business flow diagram is parsed into code as follows. All calls to the Polyv Seminar Java SDK can refer to the following call template (global initialization only needs to be called once globally).