Data request processing method and system

Abstract

The invention discloses a data request processing method and system. The method comprises the following steps: initiating requests for multiple data in an asynchronous mode by a UI thread; encapsulating the requests for the multiple data into a combined observable object by a data management class calling method, and registering the UI thread as an observer of the combined observable object; usingthe combined observable object to send the requests for the multiple data, blocking the thread called by the method, and waiting for returning a result corresponding to each request in a synchronousmode; after all the results are returned, assembling all the results by using the combined observable object, and notifying the UI thread of the assembled result; and refreshing a client interface bythe UI thread according to the assembled result. According to the technical scheme provided by the invention, multiple asynchronous network requests can be simultaneously performed without blocking amain thread, and the client interface can be prevented from being frequently refreshed.

Description

technical field [0001] The present invention relates to the communication field, in particular, to a data request processing method and system. Background technique [0002] In the Android application development process, two network request methods based on HTTP and TCP are often involved. For HTTP-based methods, there are already many mature open source solutions to handle synchronous requests and asynchronous callbacks. However, there is still a lack of mature processing solutions for processing TCP-based network requests accessed through native development tools (Native Development Kit, NDK for short), especially when it is necessary to deal with the problem of completing multiple asynchronous requests at the same time and asynchronously calling back the results at the same time . [0003] The Android application calls the network request callback interface written in C / C++ through the NDK, and these interfaces may be in different processes from the Android application...

AI Technical Summary

Problems solved by technology

If these network requests are performed separately, due to cross-process and cross-network communication, the timing of data return cannot be predicted, causing the client to refresh the interface once every callback, resulting in frequent refresh of the interface and affecting the battery life of the mobile phone And the fluency of the client, bringing bad user experience

[0004] There is such a scenario: the data that the client needs to display on a certain UI interface is completed by two or more API interfaces, and the network request cannot be made in the main thread and the main thread cannot be blocked to wait for the network request to complete

Images