1e41f4b71Sopenharmony_ci# Network Management Subsystem Changelog 2e41f4b71Sopenharmony_ci 3e41f4b71Sopenharmony_ci## request2 API Name Change 4e41f4b71Sopenharmony_ci 5e41f4b71Sopenharmony_ciChanged the name of the HTTP streaming request from **request2** to **requestInStream**. The original name **request2** does not clearly express the intent of the API and may cause ambiguity, which does not comply with the OpenHarmony API specifications. 6e41f4b71Sopenharmony_ci 7e41f4b71Sopenharmony_ci - 8e41f4b71Sopenharmony_ci 9e41f4b71Sopenharmony_ci## dataProgress Event Name Change 10e41f4b71Sopenharmony_ci 11e41f4b71Sopenharmony_ciChanged the name of the streaming data receiving event from **dataProgress** to **dataReceiveProgress**. The original name **dataProgress** does not clearly express the meaning of the event, which does not comply with the OpenHarmony API specifications. 12e41f4b71Sopenharmony_ci 13e41f4b71Sopenharmony_ci - 14e41f4b71Sopenharmony_ci 15e41f4b71Sopenharmony_ci**Change Impact** 16e41f4b71Sopenharmony_ci 17e41f4b71Sopenharmony_ciFor applications developed based on earlier versions, the corresponding API and event names must be updated. Otherwise, API calls may fail, affecting the service logic. 18e41f4b71Sopenharmony_ci 19e41f4b71Sopenharmony_ci**Key API/Component Changes** 20e41f4b71Sopenharmony_ci 21e41f4b71Sopenharmony_ciInvolved APIs: 22e41f4b71Sopenharmony_ci 23e41f4b71Sopenharmony_ci - request2; 24e41f4b71Sopenharmony_ci - on(type: "dataProgress", callback: Callback<{ receiveSize: number, totalSize: number }>): void; 25e41f4b71Sopenharmony_ci - off(type: "dataProgress", callback: Callback<{ receiveSize: number, totalSize: number }>): void; 26e41f4b71Sopenharmony_ci 27e41f4b71Sopenharmony_ciBefore change: 28e41f4b71Sopenharmony_ci - request2(url: string, callback: AsyncCallback<number>): void; 29e41f4b71Sopenharmony_ci - request2(url: string, options: HttpRequestOptions, callback: AsyncCallback<number>): void; 30e41f4b71Sopenharmony_ci - request2(url: string, options?: HttpRequestOptions): Promise<number>; 31e41f4b71Sopenharmony_ci - on(type: "dataProgress", callback: Callback<{ receiveSize: number, totalSize: number }>): void; 32e41f4b71Sopenharmony_ci - off(type: 'dataProgress', callback?: Callback<{ receiveSize: number, totalSize: number }>): void; 33e41f4b71Sopenharmony_ci 34e41f4b71Sopenharmony_ciAfter change: 35e41f4b71Sopenharmony_ci - requestInStream(url: string, callback: AsyncCallback<number>): void; 36e41f4b71Sopenharmony_ci - requestInStream(url: string, options: HttpRequestOptions, callback: AsyncCallback<number>): void; 37e41f4b71Sopenharmony_ci - requestInStream(url: string, options?: HttpRequestOptions): Promise<number>; 38e41f4b71Sopenharmony_ci - on(type: "dataReceiveProgress", callback: Callback<{ receiveSize: number, totalSize: number }>): void; 39e41f4b71Sopenharmony_ci - off(type: 'dataReceiveProgress', callback?: Callback<{ receiveSize: number, totalSize: number }>): void; 40e41f4b71Sopenharmony_ci 41e41f4b71Sopenharmony_ci**Adaptation Guide** 42e41f4b71Sopenharmony_ci 43e41f4b71Sopenharmony_ciReplace the API name **request2** and event name **dataProgress** in the original service code with **requestInStream** and **dataReceiveProgress**, respectively. 44