CN108259533B - Data transmission method and device - Google Patents

Data transmission method and device Download PDF

Info

Publication number
CN108259533B
CN108259533B CN201611240053.6A CN201611240053A CN108259533B CN 108259533 B CN108259533 B CN 108259533B CN 201611240053 A CN201611240053 A CN 201611240053A CN 108259533 B CN108259533 B CN 108259533B
Authority
CN
China
Prior art keywords
data
type
client
service
transmission channel
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201611240053.6A
Other languages
Chinese (zh)
Other versions
CN108259533A (en
Inventor
葛圆根
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201611240053.6A priority Critical patent/CN108259533B/en
Publication of CN108259533A publication Critical patent/CN108259533A/en
Application granted granted Critical
Publication of CN108259533B publication Critical patent/CN108259533B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/62Establishing a time schedule for servicing the requests
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/55Push-based network services

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application provides a data transmission method and a device, wherein the method comprises the following steps: receiving a request message for requesting at least one service data from a client; determining a service identifier corresponding to the at least one service data; acquiring first-class data corresponding to the service identifier, and sending the first-class data to the client through a first transmission channel so that the client displays the first-class data on a designated page; and acquiring second data corresponding to the service identifier, and sending the second data to the client through a second transmission channel so that the client displays the second data on the designated page. According to the technical scheme, the client can open the designated page as soon as possible, the problems that the query time of the server is long, the opening time of the designated page is too long and the like are solved, and the user experience is improved. After the server side obtains the second type of data, the second type of data can be pushed to the client side in an asynchronous mode, and real-time performance of the data is guaranteed.

Description

Data transmission method and device
Technical Field
The present application relates to the field of internet technologies, and in particular, to a data transmission method and apparatus.
Background
The client typically displays a page (referred to herein as a list page, also referred to as a feeds stream page) in the form of a list, and the list page may include a plurality of service data (e.g., feeds data), each of which is a list item in the list page. Wherein, since the list page is usually the first page of the client, the list page may contain a plurality of service data in order to make the user obtain more information from the first page.
Currently, for the display process of the list page, the client may send a request message of the list page to the server. After receiving the request message, the server needs to query each service data in sequence and return all the queried service data to the client, so that the client displays the service data on a list page.
However, in the above manner, since the service end needs to query a lot of service data, the query time is relatively long, which results in a long time for returning the service data to the client, a long time for opening the list page, and poor user experience. For example, assuming that 10 pieces of service data need to be displayed on the list page, and the query time of each piece of service data is 50 milliseconds, the time for the server to query all pieces of service data is 50 milliseconds × 10 — 500 milliseconds, and therefore, the time for the client to display the list page may exceed 500 milliseconds.
Disclosure of Invention
The application provides a data transmission method, which is applied to a server side and comprises the following steps:
receiving a request message for requesting at least one service data from a client;
determining a service identifier corresponding to the at least one service data;
acquiring first-class data corresponding to the service identifier, and sending the first-class data to the client through a first transmission channel so that the client displays the first-class data on a designated page;
and acquiring second data corresponding to the service identifier, and sending the second data to the client through a second transmission channel so that the client displays the second data on the designated page.
The application provides a data transmission method, which is applied to a client and comprises the following steps:
sending a request message for requesting at least one service data to a server;
receiving first type data sent by the server through a first transmission channel; the first type data is the first type data corresponding to the service identifier corresponding to the at least one service data acquired by the server;
displaying the first type of data on a designated page;
receiving second data transmitted by the server through a second transmission channel; the second type data is the second type data corresponding to the service identifier corresponding to the at least one service data acquired by the server;
and displaying the second type data on the specified page.
The application provides a data transmission method, which is applied to a server side and comprises the following steps:
receiving a request message for requesting at least one service data from a client; the request message is used for triggering the server to acquire first-class data and second-class data;
determining a service identifier corresponding to the at least one service data;
acquiring first-class data corresponding to the service identifier, and sending the first-class data to the client through a first transmission channel so that the client displays the first-class data on a designated page;
and acquiring second data corresponding to the service identifier, and sending the second data to the client through a second transmission channel so that the client displays the second data on the designated page.
The application provides a data transmission device, is applied to the server side, the device includes:
a receiving module, configured to receive a request message for requesting at least one service data from a client;
a determining module, configured to determine a service identifier corresponding to the at least one service data;
the first acquisition module is used for acquiring first type data corresponding to the service identifier;
the first sending module is used for sending the first type of data to the client through a first transmission channel so that the client can display the first type of data on a designated page;
the second acquisition module is used for acquiring second-class data corresponding to the service identifier;
and the second sending module is used for sending the second type of data to the client through a second transmission channel so that the client can display the second type of data on the specified page.
The application provides a data transmission device, is applied to the customer end, the device includes:
a sending module, configured to send a request message for requesting at least one service data to a server;
the first receiving module is used for receiving first type data sent by the server through a first transmission channel; the first type data is the first type data corresponding to the service identifier corresponding to the at least one service data acquired by the server;
the first display module is used for displaying the first type of data on a specified page;
the second receiving module is used for receiving second type data sent by the server through a second transmission channel; the second type of data is second type of data corresponding to a service identifier corresponding to the at least one service data acquired by the server;
and the second display module is used for displaying the second type of data on the specified page.
The application provides a data transmission device, is applied to the server side, the device includes:
a receiving module, configured to receive a request message for requesting at least one service data from a client; the request message is used for triggering the server to acquire first-class data and second-class data;
a determining module, configured to determine a service identifier corresponding to the at least one service data;
the first acquisition module is used for acquiring first type data corresponding to the service identifier;
the first sending module is used for sending the first type of data to the client through a first transmission channel so that the client can display the first type of data on a designated page;
the second acquisition module is used for acquiring second-class data corresponding to the service identifier;
and the second sending module is used for sending the second type of data to the client through a second transmission channel so that the client can display the second type of data on the specified page.
Based on the above technical solution, in the embodiment of the application, after receiving the request message, the server may separate the first type of data and the second type of data of the service data, and then obtain the first type of data first, and send the first type of data to the client, so that the client displays the first type of data on the designated page. Therefore, the query time of the first type of data is short, and the server can send the first type of data to the client in a short time, so that the client can open the designated page as soon as possible, the problems that the query time of the server is long, the opening time of the designated page is too long and the like are solved, and the user experience is improved. After the server side obtains the second type of data, the second type of data can be pushed to the client side in an asynchronous mode, and therefore real-time performance of the data is guaranteed.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present application or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present application;
FIG. 2 is a flow chart of a data transmission method in one embodiment of the present application;
FIG. 3 is a flow chart of a data transmission method in another embodiment of the present application;
FIG. 4 is a flow chart of a data transmission method in another embodiment of the present application;
FIG. 5A is a flow chart of a data transmission method in another embodiment of the present application;
FIGS. 5B and 5C are schematic diagrams of a list page in one embodiment of the present application;
FIG. 6 is a diagram of a hardware configuration of a server in one embodiment of the present application;
fig. 7 is a block diagram of a data transmission device according to an embodiment of the present application;
fig. 8 is a block diagram of a data transmission device according to another embodiment of the present application;
FIG. 9 is a diagram of a hardware configuration of a client in one embodiment of the present application;
fig. 10 is a block diagram of a data transfer device according to an embodiment of the present application.
Detailed Description
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein is meant to encompass any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Depending on the context, moreover, the word "if" may be used is interpreted as "at … …," or "at … …," or "in response to a determination.
The embodiment of the present application provides a data transmission method, which may be applied to a system including a client and a server, as shown in fig. 1, and is a schematic structural diagram of the system. The client may be an APP (Application) on a terminal device (e.g., a PC (Personal Computer), a notebook Computer, a mobile terminal, etc.), and the type of the client is not limited, and all clients capable of accessing the server are within the scope of the embodiments of the present Application. The server is a device having a data acquisition function and a data transmission function, for example, the server may be a data platform, an e-commerce platform, and the like, the type of the server is not limited, and all devices having a data acquisition function and a data transmission function are within the protection scope of the embodiment of the present application. Referring to fig. 2, a flowchart of a data transmission method in the embodiment of the present application is shown, where the method may be applied to a server, and the method may include the following steps:
step 201, a request message for requesting at least one service data is received from a client.
Step 202, determining a service identifier corresponding to the at least one service data.
Step 203, obtaining the first type data corresponding to the service identifier, and sending the first type data to the client through the first transmission channel, so that the client displays the first type data on the designated page.
Step 204, obtaining the second type data corresponding to the service identifier, and sending the second type data to the client through the second transmission channel, so that the client displays the second type data on the designated page.
In an example, the execution sequence is only an example given for convenience of description, and in practical applications, the execution sequence between the steps may also be changed, and the execution sequence is not limited.
Referring to step 201, in an example, when a client needs to display at least one service data through a designated page, the client sends a request message to a server, where the request message is used to request the server for the at least one service data. In this way, the server may receive a request message for requesting the at least one service data from the client. Wherein the designated page may include, but is not limited to: a page that needs to be displayed in list form (this page may be referred to as a list page, also referred to as a feeds stream page); a page to be displayed in a text box form; a page to be displayed in the form of a picture; a page displayed in a character string form is required, and the type of the specified page is not limited as long as at least one service data (for example, for a list page, the service data may be referred to as feed data) can be displayed through the specified page.
With reference to step 202, in an example, after receiving the request message, the server may determine a service identifier corresponding to the at least one service data. For example, the request message sent by the client may carry a service identifier corresponding to the at least one service data, so that the server may analyze the service identifier corresponding to the at least one service data from the request message. For another example, the request message sent by the client may carry a request parameter, where the request parameter corresponds to a service identifier corresponding to at least one service data, so that the server may parse the request parameter from the request message, and obtain the service identifier corresponding to the at least one service data by querying a corresponding relationship between the request parameter and the service identifier.
For convenience of description, the request message is used to request the service data 1, the service data 2, and the service data 3 as an example, of course, the number of the requested service data may be more than three, and the number is not limited to this, and the following description will take the example of requesting three service data as an example. Based on this, the service end can determine the service identifier 1 corresponding to the service data 1, the service identifier 2 corresponding to the service data 2, and the service identifier 3 corresponding to the service data 3.
For step 203 and step 204, after determining the service identifier, the server does not acquire the service data corresponding to the service identifier, but divides the service data into first-class data and second-class data, and the server first acquires the first-class data corresponding to the service identifier, sends the first-class data to the client through the first transmission channel, then acquires the second-class data corresponding to the service identifier, and sends the second-class data to the client through the second transmission channel. The first transmission channel used when the server side sends the first type of data to the client side is different from the second transmission channel used when the server side sends the second type of data to the client side.
In practical applications, the service data may include many data, and each data included in the service data is referred to as sub data. Of course, the dividing manner of the first type data and the second type data is not limited to the above manner, and the dividing manner is not limited thereto.
For the process of dividing the sub-data included in the service data into the first type of data and the second type of data according to the obtaining time of the sub-data, the sub-data whose obtaining time (i.e. the time from the time when the request message is received by the server to the time when the sub-data is obtained) is less than a preset time threshold (e.g. 30 milliseconds) may be determined as the first type of data, and the sub-data whose obtaining time is not less than the preset time threshold may be determined as the second type of data.
In the process of dividing the sub-data included in the service data into the first-class data and the second-class data according to the user requirement, the sub-data that needs to be displayed first on the designated page (i.e., the sub-data that should be simultaneously viewed when the user sees the designated page) may be determined as the first-class data, and the sub-data that does not need to be displayed first on the designated page (i.e., the sub-data that may not be viewed first when the user sees the designated page, as long as the sub-data that can be viewed in the subsequent display process of the designated page) may be determined as the second-class data.
In the process of dividing the sub data included in the service data into the first type of data and the second type of data according to the obtaining time of the sub data and the user requirement, the obtaining time may be smaller than a preset time threshold (for example, 30 milliseconds), and the sub data that needs to be displayed first on a designated page is determined as the first type of data, and other sub data except the first type of data included in the service data is determined as the second type of data.
Of course, in practical application, it may also be determined that part of the sub data of the service data is the first type of data according to other policies, and that other sub data other than the first type of data is the second type of data, which is not described again.
In summary, since the server can obtain information such as the acquisition time of the data and the user requirement, the server dominates asynchronization, that is, separation of the first type of data and the second type of data, and sends the first type of data and the second type of data to the client by using different transmission channels in the embodiment of the present application. Compared to client-dominated asynchrony: firstly, if the client side dominates asynchronization, after the page development is completed, the page opening data is discovered to be slow based on user feedback possibly after online operation and maintenance is carried out for a period of time, asynchronous transformation is needed, and the discovery of the client side has hysteresis. If the server side dominates asynchronization, after the page development is completed, the server side has a large amount of performance data of interfaces, so that the slow page opening data can be found in advance, asynchronous transformation is performed in advance, and the processing is timely. Secondly, if the client is asynchronous, the client can know the query performance of the page data to the server, then the server separates the data interface into a plurality of data interfaces, and the client can send a plurality of requests to the server. If the server side is asynchronous, the server side knows the dependency relationship between the data A and the data B, does not need to wait until the data A is returned to the client side and receives the request of the data B to inquire the data B, but can synchronously inquire the data B when inquiring the data A, and the transmission time of the data B is saved. And if the client dominates asynchronization, asynchronization is performed for each specific scene each time, for example, when a problem is found in the page a, the page a is processed asynchronously, when a problem is found in the page B, the page B is processed asynchronously, development of the client and the server is required each time, and after the client is modified, a series of complicated processes such as upgrading are required, so that the modification cost is high. Moreover, such clients have not been able to implement asynchronous processing if the user is unwilling to upgrade the version of the client. If the server side leads asynchronization, the performance optimization of the page is completely at the server side, the client side does not need to be upgraded, and if the A page has problems, the server side data interface corresponding to the A page is directly transformed into synchronous and asynchronous combination. And if the B page has problems, directly transforming the server data interface corresponding to the B page into synchronous and asynchronous combination.
In one example, after the client sends the request message to the server, the server returns a response message for the request message to the client, and the request message and the response message are in the same transmission channel, for example, when the request message is an HTTP (HyperText Transfer Protocol) request message, the response message is an HTTP response message, and the transmission channel is an HTTP transmission channel. Therefore, the first transmission channel may be a transmission channel corresponding to the request message, that is, the server may send the first type of data to the client through the response message of the request message, and the client displays the first type of data on the designated page.
After the server returns a response message for the request message to the client, the first transmission channel between the client and the server is interrupted, the server cannot send the second type of data to the client through the first transmission channel again, and the server sends the response message to the client through the first transmission channel only after receiving the request message from the client again. In the embodiment of the present application, in order to request the same service data, the client only sends a request message to the server once, but does not send the request message to the server multiple times, so that the server cannot send the second type of data to the client through the first transmission channel, and needs to send the second type of data to the client through other transmission channels. Based on this, the service end may also determine a transmission mode of the second type of data, a channel corresponding to the transmission mode is referred to as a second transmission channel, and the transmission mode is information of the second transmission channel. Therefore, the server can send the second type data to the client through the second transmission channel.
In one example, the second transmission channel may include, but is not limited to: a PUSH (PUSH) channel between a server and a client, where the PUSH channel is a technology in which the server actively sends data to the client, and all ways in which the server actively sends data to the client are within the protection scope of the embodiment of the present application.
In one example, after the client sends the request message to the server through the first transmission channel, the client knows that the server returns a response message to the client, and therefore, the client can monitor the response message received on the first transmission channel, then monitor the response message, and parse the first type of data from the response message. However, if the client does not know the information of the second transmission channel, the client does not monitor the data received by the client on the second transmission channel, so that the client cannot obtain the second type of data.
Based on this, in the process that the server sends the first type of data to the client through the first transmission channel, the transmission modes of the first type of data and the second type of data (i.e. the information of the second transmission channel) can be sent to the client through the first transmission channel. In this way, the client can determine that the second transmission channel is used when the server sends the second type of data by using the transmission mode, and then monitor the data received by the client on the second transmission channel to monitor the second type of data sent by the server through the second transmission channel.
In practical application, the client can support one-time request of the client through the underlying framework, and can receive data returned by the server through a plurality of transmission channels. Thus, as long as the underlying framework of the client supports, even if the client accepts a new service and develops a new page, it is not necessary to know what way (e.g., synchronous, asynchronous, a combination of synchronous and asynchronous, etc.) the underlying data is received.
For step 204, in an example, for a process of "the server obtains the second type data corresponding to the service identifier", when the number of the service identifiers is multiple, the server may obtain the second type data corresponding to each service identifier in a synchronous manner; or, the server may further acquire the second type data corresponding to each service identifier in an asynchronous manner. Wherein, the asynchronous mode may include, but is not limited to, the following modes: a multithreading mode, a coroutine mode, and an asynchronous IO (Input Output) concurrency mode.
For example, when the service identifier is the service identifier 1, the service identifier 2, and the service identifier 3, in terms of the process of "the server side acquires the second type data in a synchronous manner", the server side acquires the second type data corresponding to the service identifier 1, acquires the second type data corresponding to the service identifier 2 after the second type data corresponding to the service identifier 1 is successfully acquired, and acquires the second type data corresponding to the service identifier 3 after the second type data corresponding to the service identifier 2 is successfully acquired. Aiming at the process that the server side acquires the second type data in an asynchronous mode, the server side can simultaneously acquire the second type data corresponding to the service identifier 1, the second type data corresponding to the service identifier 2 and the second type data corresponding to the service identifier 3.
In an example, the process for "the server sends the second type data to the client through the second transmission channel" may include, but is not limited to, the following ways: after second-class data corresponding to one service identifier is obtained, the server side sends the second-class data corresponding to the service identifier to the client side through a second transmission channel; or after the second-class data corresponding to all the service identifiers are obtained, the server sends the second-class data corresponding to all the service identifiers to the client through the second transmission channel. For example, after acquiring the second type of data corresponding to the service identifier 1, the server sends the second type of data corresponding to the service identifier 1 to the client through the second transmission channel. And after the second type data corresponding to the service identifier 2 is obtained, the second type data corresponding to the service identifier 2 is sent to the client through a second transmission channel. And after the second type data corresponding to the service identifier 3 is obtained, the second type data corresponding to the service identifier 3 is sent to the client through a second transmission channel. Or after the server acquires the second type data corresponding to the service identifier 1, the second type data corresponding to the service identifier 2, and the second type data corresponding to the service identifier 3, the server sends the second type data corresponding to the service identifier 1, the second type data corresponding to the service identifier 2, and the second type data corresponding to the service identifier 3 to the client through the second transmission channel.
Based on the above technical solution, in the embodiment of the application, after receiving the request message, the server may separate the first type of data and the second type of data of the service data, and then obtain the first type of data first, and send the first type of data to the client, so that the client displays the first type of data on the designated page. Therefore, the query time of the first type of data is short, and the server can send the first type of data to the client in a short time, so that the client can open the designated page as soon as possible, the problems that the query time of the server is long, the opening time of the designated page is too long and the like are solved, and the user experience is improved. After the server side obtains the second type of data, the second type of data can be pushed to the client side in an asynchronous mode, and therefore real-time performance of the data is guaranteed.
Based on the same application concept as the above method, referring to fig. 3, which is a flowchart of a data transmission method in the embodiment of the present application, the method may be applied to a client, and the method may include the following steps:
step 301, sending a request message for requesting at least one service data to a server.
Step 302, receiving first type data sent by a server through a first transmission channel; the first type data is the first type data corresponding to the service identifier corresponding to at least one service data acquired by the server.
Step 303, displaying the first type of data on a designated page.
Step 304, receiving second type data sent by the server through a second transmission channel; the second type data is the second type data corresponding to the service identifier corresponding to at least one service data acquired by the server.
Step 305, displaying the second type data on the specified page.
In one example, the procedure for "receiving the first type of data sent by the server through the first transmission channel" may include, but is not limited to: the client receives the transmission modes of the first type data and the second type data sent by the server through the first transmission channel; the transmission mode is specifically information of the second transmission channel.
In an example, the process for "receiving the second type data sent by the server through the second transmission channel" may include, but is not limited to: the client determines a second transmission channel used when the server sends the second type of data by using the transmission mode of the second type of data, and monitors the data received by the client on the second transmission channel so as to monitor the second type of data sent by the server through the second transmission channel.
In one example, the first transmission channel may include, but is not limited to: a transmission channel corresponding to the request message; the second transmission channel may include, but is not limited to: and a push channel between the server side and the client side.
In one example, the process for "displaying the first type of data on the designated page" may include, but is not limited to, the following: the client acquires a page identifier corresponding to the first type of data, and displays the first type of data on a designated page corresponding to the page identifier. The process for "displaying the second type data on the designated page" may include, but is not limited to, the following: and the client acquires the page identification corresponding to the second type of data and displays the second type of data on the specified page corresponding to the page identification.
The request message sent by the client to the server can also carry a page identifier of the specified page. Based on this, when the server sends the first type of data to the client through the first transmission channel, the page identifier may also be carried in the sent message, so that the client obtains the page identifier corresponding to the first type of data. And when the server sends the second type of data to the client through the second transmission channel, the page identifier can be carried in the sent message, so that the client can acquire the page identifier corresponding to the second type of data.
Based on the above technical solution, in the embodiment of the application, after receiving the request message, the server may separate the first type of data and the second type of data of the service data, and then obtain the first type of data first, and send the first type of data to the client, so that the client displays the first type of data on the designated page. Therefore, the query time of the first type of data is short, and the server can send the first type of data to the client in a short time, so that the client can open the designated page as soon as possible, the problems that the query time of the server is long, the opening time of the designated page is too long and the like are solved, and the user experience is improved. After the server side obtains the second type of data, the second type of data can be pushed to the client side in an asynchronous mode, and therefore real-time performance of the data is guaranteed.
Based on the same application concept as the above method, referring to fig. 4, which is a flowchart of a data transmission method in the embodiment of the present application, the method may be applied to a server, and the method may include the following steps:
step 401, receiving a request message for requesting at least one service data from a client; the request message is used for triggering the server to acquire the first type of data and the second type of data.
Step 402, determining a service identifier corresponding to the at least one service data.
Step 403, obtaining the first type of data corresponding to the service identifier, and sending the first type of data to the client through a first transmission channel, so that the client displays the first type of data on a designated page.
Step 404, obtaining the second type data corresponding to the service identifier, and sending the second type data to the client through a second transmission channel, so that the client displays the second type data on a designated page.
In one example, the client may dominate the asynchronous process, that is, the client may send a request message to the server, where the request message is used to trigger the server to obtain the first type of data, and return the first type of data to the client. Then, the client may send another request message to the server, where the request message is used to trigger the server to obtain the second type of data, and return the second type of data to the client.
In another example, the asynchronous process may be further dominated by the server, that is, the client sends only one request message to the server, where the request message is used to trigger the server to obtain the first type of data and the second type of data, but not to trigger the server to obtain the first type of data, so that the server may obtain the first type of data and return the first type of data to the client, and the server may obtain the second type of data and return the second type of data to the client, but not to obtain the second type of data based on another request message from the client.
Other processing procedures of the flow are similar to those shown in fig. 2, and are not repeated herein.
The above technical solution of the embodiments of the present application is described in detail below with reference to specific application scenarios.
As shown in fig. 5A, a flowchart of a data transmission method in an embodiment of the present application is shown, where the method includes:
in step 501, when a specified page (such as a list page, which is described later by taking the list page as an example) needs to be displayed, the client generates a request message for requesting service data, where the request message may include a request parameter and a page identifier of the list page.
Step 502, the client sends the request message to the server.
Step 503, the server receives the request message sent by the client, and parses the request parameter from the request message.
Step 504, the service end determines the service identifier corresponding to the request parameter.
For example, when the client needs to display a list page of goods, the request parameter may be user identification (indicating that the list page is displayed to the user) + goods (indicating that business data related to the goods is requested). After obtaining the user identifier, the server may query historical data corresponding to the user identifier from the local database, find historical data related to the goods from the historical data, and determine goods concerned by the user based on the historical data related to the goods, where names of the goods are service identifiers corresponding to the request parameters. Of course, the above is only an example of determining the service identifier, and is not limited to this in practical application, and the determination manner of the service identifier may be different according to different application scenarios, and is not described again.
Step 505, the server obtains the transmission mode of the first type data and the second type data corresponding to the service identifier.
Step 506, the server sends the first type of data and the transmission mode (i.e. the transmission mode of the second type of data) to the client through the first transmission channel.
In step 507, the client displays the first type of data on the list page and sets a listener. After receiving the first type of data and the transmission mode of the second type of data (such as information of the second transmission channel), the client may determine the second transmission channel used when the server sends the second type of data by using the transmission mode, and set a listener, and listen to the data received by the client on the second transmission channel by using the listener. The first transmission channel may include, but is not limited to: the transmission channel corresponding to the request message, the second transmission channel may include but is not limited to: and a push channel between the server side and the client side.
The business data can be divided into a first type of data and a second type of data, for example, the first type of data can be data of title, picture, description, merchant, etc. of the goods, and the second type of data can be data of total number of goods in sales of the merchant, total number of agents of the merchant, etc. Since the first type of data of the title, the picture, the description, the merchant, and the like of the commodity are stored in the local database, the server can query the first type of data corresponding to the service identifier from the local database, send the first type of data to the client through the first transmission channel, and display the first type of data on a list page by the client, as shown in fig. 5B, which is an example of the list page.
Step 508, the server obtains the second type data corresponding to the service identifier.
In step 509, the server sends the second type data to the client through the second transmission channel.
In step 510, the client displays the second type data on the list page.
In one example, the second type of data is maintained by the service end, in order to obtain the second type of data, the service end sends an RPC (Remote Procedure Call Protocol) request message carrying a service identifier to the service end, and after receiving the RPC request message, the service end queries the second type of data corresponding to the service identifier and returns the queried second type of data to the service end through an RPC response message.
The service end can send the RPC request message carrying the service identifier to the service end in an asynchronous manner (such as multithreading, coroutine, asynchronous IO concurrency, and the like). For example, the server sends an RPC request message 1 carrying a service identifier 1, an RPC request message 2 carrying a service identifier 2, and the like to the service at the same time.
In an example, after the service end sends the RPC request message to the service end, a listener may be further configured, and the listener is used to listen to the second type of data returned by the service end. After monitoring all the second-class data returned by the service end, the service end can also send the second-class data to the client through a second transmission channel (such as a message channel, a sync push and other push modes) between the service end and the client.
Since the listener of the client is configured to listen to the data received by the client on the second transmission channel, the client may listen to the second type of data sent by the server through the second transmission channel, and display the second type of data on a designated page, as shown in fig. 5C, which is an example of the designated page.
In an example, when the server sends the first type of data to the client, the server may further send a page identifier of a designated page, so that the client may obtain the page identifier corresponding to the first type of data and display the first type of data on the designated page corresponding to the page identifier. And when the server side sends the second type data to the client side, the server side can also send the page identification of the specified page, so that the client side can obtain the page identification corresponding to the second type data and display the second type data on the specified page corresponding to the page identification.
Based on the above technical solution, in the embodiment of the application, after receiving the request message, the server may separate the first type of data and the second type of data of the service data, and then obtain the first type of data first, and send the first type of data to the client, so that the client displays the first type of data on the designated page. Because the query time of the first type of data is short, the server can send the first type of data to the client in a short time, so that the client can open the designated page as soon as possible, the problems that the query time of the server is long, the opening time of the designated page is too long and the like are solved, and the user experience is improved. After the server side obtains the second type of data, the second type of data can be pushed to the client side in an asynchronous mode, and therefore real-time performance of the data is guaranteed.
Based on the same application concept as the method, the embodiment of the present application further provides a data transmission apparatus 120, where the data transmission apparatus 120 can be applied to the server 10. The data transmission device 120 may be implemented by software, or may be implemented by hardware, or a combination of hardware and software. Taking a software implementation as an example, a device in a logical sense is formed by reading corresponding computer program instructions in the non-volatile memory 12 through the processor 11 of the server 10 where the device is located. From a hardware level, as shown in fig. 6, the hardware structure of the service end 10 where the data transmission device 120 is located is shown, and besides the processor 11 and the nonvolatile memory 12 shown in fig. 6, the service end 10 may further include other hardware, such as a forwarding chip, a network interface, and a memory, which are responsible for processing a packet; in terms of hardware structure, the server 10 may also be a distributed device, and may include a plurality of interface cards, so as to perform an extension of the message processing at a hardware level.
As shown in fig. 7, a block diagram of a data transmission device proposed in the present application includes: a receiving module 1201, configured to receive a request message from a client for requesting at least one service data;
a determining module 1202, configured to determine a service identifier corresponding to the at least one service data;
a first obtaining module 1203, configured to obtain first type data corresponding to the service identifier;
a first sending module 1204, configured to send the first type of data to the client through a first transmission channel, so that the client displays the first type of data on a specified page;
a second obtaining module 1205, configured to obtain second type data corresponding to the service identifier;
a second sending module 1206, configured to send the second type of data to the client through a second transmission channel, so that the client displays the second type of data on the specified page.
The first sending module 1204 is specifically configured to determine a transmission mode of second type data in a process of sending the first type data to the client through a first transmission channel, where the transmission mode is information of the second transmission channel; sending the first type of data and the transmission mode to the client through a first transmission channel; the first transmission channel specifically comprises: a transmission channel corresponding to the request message; the second transmission channel specifically includes: and a push channel between the server and the client.
The second obtaining module 1205 is specifically configured to, in the process of obtaining a plurality of second-class data corresponding to the service identifier, obtain, in a synchronous manner, the second-class data corresponding to each service identifier when the number of the service identifiers is multiple; or, acquiring second-class data corresponding to each service identifier in an asynchronous mode;
wherein the asynchronous mode comprises: a multithreading mode, a coroutine mode and an asynchronous IO concurrent mode.
In an example, the second sending module 1206 is specifically configured to, in a process of sending the second type of data to the client through a second transmission channel, after obtaining the second type of data corresponding to one service identifier, send the second type of data corresponding to the one service identifier to the client through the second transmission channel; or after the second-class data corresponding to all the service identifications are obtained, the second-class data corresponding to all the service identifications are sent to the client through a second transmission channel.
As shown in fig. 8, a block diagram of a data transmission device proposed in the present application includes:
a receiving module 1207, configured to receive a request message for requesting at least one service data from a client; the request message is used for triggering the server to acquire the first type of data and the second type of data;
a determining module 1208, configured to determine a service identifier corresponding to the at least one service data;
a first obtaining module 1209, configured to obtain first type data corresponding to the service identifier;
a first sending module 1210, configured to send the first type of data to the client through a first transmission channel, so that the client displays the first type of data on a specified page;
a second obtaining module 1211, configured to obtain second class data corresponding to the service identifier;
a second sending module 1212, configured to send the second type of data to the client through a second transmission channel, so that the client displays the second type of data on the specified page.
Based on the same application concept as the method, the embodiment of the present application further provides a data transmission apparatus 220, and the data transmission apparatus 220 can be applied to the client 20. The data transmission device 220 may be implemented by software, or may be implemented by hardware or a combination of hardware and software. A logical device, implemented in software for example, is formed by the processor 21 of the client 20 reading corresponding computer program instructions in the non-volatile memory 22. From a hardware level, as shown in fig. 9, it is a hardware structure diagram of the client 20 where the data transmission device 220 is located, and besides the processor 21 and the nonvolatile memory 22 shown in fig. 9, the client 20 may also include other hardware, such as a forwarding chip, a network interface, and a memory, which are responsible for processing a message; the client 20 may also be a distributed device in terms of hardware structure, and may include a plurality of interface cards to extend the message processing at the hardware level.
As shown in fig. 10, a block diagram of a data transmission device proposed in the present application includes:
a sending module 2201, configured to send a request message for requesting at least one service data to a server;
a first receiving module 2202, configured to receive first type data sent by the server through a first transmission channel; the first type data is the first type data corresponding to the service identifier corresponding to the at least one service data acquired by the server;
a first display module 2203, configured to display the first type of data on a designated page;
a second receiving module 2204, configured to receive the second type of data sent by the server through a second transmission channel; the second type of data is second type of data corresponding to a service identifier corresponding to the at least one service data acquired by the server;
a second display module 2205, configured to display the second type of data on the designated page.
The first receiving module 2202 is specifically configured to receive a transmission mode of first type data and second type data sent by the server through a first transmission channel in a process of receiving the first type data sent by the server through the first transmission channel; the transmission mode is specifically information of the second transmission channel;
the second receiving module 2204 is specifically configured to, in a process of receiving second type data sent by the server through a second transmission channel, determine, by using the transmission manner, a second transmission channel used when the server sends the second type data; monitoring data received by the client on the second transmission channel so as to monitor second type data sent by the server through the second transmission channel;
wherein, the first transmission channel specifically includes: a transmission channel corresponding to the request message;
the second transmission channel specifically includes: and a push channel between the server and the client.
The first display module 2203 is specifically configured to obtain a page identifier corresponding to the first type of data; displaying the first type of data on a designated page corresponding to the page identifier;
the second display module 2205 is specifically configured to obtain a page identifier corresponding to the second type of data; and displaying the second type of data on a specified page corresponding to the page identifier.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (which may include, but is not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims (17)

1. A data transmission method is applied to a server side, and is characterized in that the method comprises the following steps:
receiving a request message for requesting at least one service data from a client;
determining a service identifier corresponding to the at least one service data;
acquiring first-class data corresponding to the service identifier, and sending the transmission mode of the first-class data and the second-class data to the client through a first transmission channel so that the client displays the first-class data on a designated page;
after the first type of data corresponding to the service identifier is obtained, second type of data corresponding to the service identifier is obtained, and the second type of data is sent to the client through a second transmission channel, so that the client can display the second type of data on the designated page;
the service data comprises a plurality of subdata, and the subdata contained in the service data is divided into first-class data and second-class data according to the acquisition time of the subdata; or, dividing the sub data included in the service data into the first type data and the second type data according to the obtaining time of the sub data and the user requirement.
2. The method according to claim 1, wherein the process of sending the transmission modes of the first type of data and the second type of data to the client via the first transmission channel specifically includes:
determining a transmission mode of second type data, wherein the transmission mode is information of the second transmission channel;
and sending the first type of data and the transmission mode to the client through a first transmission channel.
3. The method according to claim 1 or 2,
the first transmission channel specifically comprises: a transmission channel corresponding to the request message;
the second transmission channel specifically includes: and a push channel between the server and the client.
4. The method according to claim 1, wherein when the number of the service identifiers is multiple, the process of obtaining the second type of data corresponding to the service identifiers specifically includes:
acquiring second-class data corresponding to each service identifier in a synchronous mode; alternatively, the first and second electrodes may be,
acquiring second-class data corresponding to each service identifier in an asynchronous mode;
wherein the asynchronous mode comprises: a multithreading mode, a coroutine mode and an asynchronous IO concurrent mode.
5. The method according to claim 4, wherein the process of sending the second type of data to the client via a second transmission channel specifically includes:
after second-class data corresponding to one service identifier is obtained, the second-class data corresponding to the service identifier is sent to the client through a second transmission channel; alternatively, the first and second electrodes may be,
and after the second-class data corresponding to all the service identifications are obtained, the second-class data corresponding to all the service identifications are sent to the client through a second transmission channel.
6. A data transmission method is applied to a client, and is characterized in that the method comprises the following steps:
sending a request message for requesting at least one service data to a server;
receiving a transmission mode of first type data and second type data sent by the server through a first transmission channel, wherein the transmission mode is specifically information of a second transmission channel; the first type data is the first type data corresponding to the service identifier corresponding to the at least one service data acquired by the server;
displaying the first type of data on a designated page;
determining a second transmission channel used when a server sends second type data by using the transmission mode, and monitoring data received by the client on the second transmission channel so as to receive the second type data sent by the server through the second transmission channel; the second type data is the second type data corresponding to the service identifier corresponding to the at least one service data, which is obtained after the server obtains the first type data corresponding to the service identifier corresponding to the at least one service data;
displaying the second type data on the designated page;
the service data comprises a plurality of subdata, and the subdata contained in the service data is divided into first-class data and second-class data according to the acquisition time of the subdata; or, dividing the sub data included in the service data into the first type data and the second type data according to the obtaining time of the sub data and the user requirement.
7. The method of claim 6,
the first transmission channel specifically comprises: a transmission channel corresponding to the request message;
the second transmission channel specifically includes: and a push channel between the server and the client.
8. The method of claim 6,
the process of displaying the first type of data on the designated page specifically includes:
acquiring a page identifier corresponding to the first type of data;
displaying the first type of data on a designated page corresponding to the page identifier;
the process of displaying the second type of data on the designated page specifically includes:
acquiring a page identifier corresponding to the second type of data;
and displaying the second type of data on a specified page corresponding to the page identifier.
9. A data transmission method is applied to a server side, and is characterized in that the method comprises the following steps:
receiving a request message for requesting at least one service data from a client; the request message is used for triggering the server to acquire first-class data and second-class data;
determining a service identifier corresponding to the at least one service data;
acquiring first-class data corresponding to the service identifier, and sending the transmission mode of the first-class data and the second-class data to the client through a first transmission channel so that the client displays the first-class data on a designated page;
after the first type of data corresponding to the service identifier is obtained, second type of data corresponding to the service identifier is obtained, and the second type of data is sent to the client through a second transmission channel, so that the client can display the second type of data on the designated page;
the service data comprises a plurality of subdata, and the subdata contained in the service data is divided into first-class data and second-class data according to the acquisition time of the subdata; or, dividing the sub data included in the service data into the first type data and the second type data according to the obtaining time of the sub data and the user requirement.
10. A data transmission apparatus applied to a server, the apparatus comprising:
a receiving module, configured to receive a request message for requesting at least one service data from a client;
a determining module, configured to determine a service identifier corresponding to the at least one service data;
the first acquisition module is used for acquiring first type data corresponding to the service identifier;
the first sending module is used for sending the transmission modes of the first type data and the second type data to the client through a first transmission channel so that the client can display the first type data on a designated page;
the second acquisition module is used for acquiring second type data corresponding to the service identifier after acquiring the first type data corresponding to the service identifier;
the second sending module is used for sending the second type of data to the client through a second transmission channel so that the client can display the second type of data on the designated page;
the service data comprises a plurality of subdata, and the subdata contained in the service data is divided into first-class data and second-class data according to the acquisition time of the subdata; or, dividing the sub data included in the service data into the first type data and the second type data according to the obtaining time of the sub data and the user requirement.
11. The apparatus according to claim 10, wherein the first sending module is specifically configured to determine a transmission mode of the second type of data in a process of sending the transmission modes of the first type of data and the second type of data to the client through a first transmission channel, where the transmission mode is information of the second transmission channel; sending the first type of data and the transmission mode to the client through a first transmission channel;
wherein, the first transmission channel specifically includes: a transmission channel corresponding to the request message;
the second transmission channel specifically includes: and a push channel between the server and the client.
12. The apparatus of claim 10,
the second obtaining module is specifically configured to, in a process of obtaining the second type data corresponding to the service identifier, obtain, in a synchronous manner, the second type data corresponding to each service identifier when the number of the service identifiers is multiple; or, acquiring second-class data corresponding to each service identifier in an asynchronous mode;
wherein the asynchronous mode comprises: a multithreading mode, a coroutine mode and an asynchronous IO concurrent mode.
13. The apparatus of claim 12,
the second sending module is specifically configured to, in a process of sending the second type of data to the client through a second transmission channel, send the second type of data corresponding to one service identifier to the client through a second transmission channel after the second type of data corresponding to the one service identifier is obtained; alternatively, the first and second electrodes may be,
and after the second-class data corresponding to all the service identifications are obtained, the second-class data corresponding to all the service identifications are sent to the client through a second transmission channel.
14. A data transmission apparatus applied to a client, the apparatus comprising:
a sending module, configured to send a request message for requesting at least one service data to a server;
the first receiving module is used for receiving a transmission mode of first type data and second type data sent by the server through a first transmission channel, wherein the transmission mode is specifically information of a second transmission channel; the first type data is the first type data corresponding to the service identifier corresponding to the at least one service data acquired by the server;
the first display module is used for displaying the first type of data on a specified page;
the second receiving module is used for determining a second transmission channel used when the server sends the second type of data by using the transmission mode, and monitoring the data received by the client on the second transmission channel so as to receive the second type of data sent by the server through the second transmission channel; the second type of data is the second type of data corresponding to the service identifier corresponding to the at least one service data, which is obtained after the server obtains the first type of data corresponding to the service identifier corresponding to the at least one service data;
the second display module is used for displaying the second type of data on the specified page;
the service data comprises a plurality of subdata, and the subdata contained in the service data is divided into first-class data and second-class data according to the acquisition time of the subdata; or, dividing the sub data included in the service data into the first type data and the second type data according to the obtaining time of the sub data and the user requirement.
15. The apparatus of claim 14,
wherein, the first transmission channel specifically includes: a transmission channel corresponding to the request message;
the second transmission channel specifically includes: and a push channel between the server and the client.
16. The apparatus of claim 14,
the first display module is specifically configured to obtain a page identifier corresponding to the first type of data; displaying the first type of data on a designated page corresponding to the page identifier;
the second display module is specifically configured to obtain a page identifier corresponding to the second type of data; and displaying the second type of data on a specified page corresponding to the page identifier.
17. A data transmission apparatus applied to a server, the apparatus comprising:
a receiving module, configured to receive a request message for requesting at least one service data from a client; the request message is used for triggering the server to acquire first-class data and second-class data;
a determining module, configured to determine a service identifier corresponding to the at least one service data;
the first acquisition module is used for acquiring first type data corresponding to the service identifier;
the first sending module is used for sending the transmission modes of the first type data and the second type data to the client through a first transmission channel so that the client can display the first type data on a designated page;
the second acquisition module is used for acquiring second type data corresponding to the service identifier after acquiring the first type data corresponding to the service identifier;
the second sending module is used for sending the second type of data to the client through a second transmission channel so that the client can display the second type of data on the designated page;
the service data comprises a plurality of subdata, and the subdata contained in the service data is divided into first-class data and second-class data according to the acquisition time of the subdata; or, dividing the sub data included in the service data into the first type data and the second type data according to the obtaining time of the sub data and the user requirement.
CN201611240053.6A 2016-12-28 2016-12-28 Data transmission method and device Active CN108259533B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201611240053.6A CN108259533B (en) 2016-12-28 2016-12-28 Data transmission method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201611240053.6A CN108259533B (en) 2016-12-28 2016-12-28 Data transmission method and device

Publications (2)

Publication Number Publication Date
CN108259533A CN108259533A (en) 2018-07-06
CN108259533B true CN108259533B (en) 2022-03-04

Family

ID=62719841

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201611240053.6A Active CN108259533B (en) 2016-12-28 2016-12-28 Data transmission method and device

Country Status (1)

Country Link
CN (1) CN108259533B (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109408750A (en) * 2018-09-26 2019-03-01 中国平安财产保险股份有限公司 Page display method, device, computer equipment and storage medium
CN110177126A (en) * 2019-04-04 2019-08-27 口碑(上海)信息技术有限公司 Data communication method, the apparatus and system in unified message channel
CN110943886B (en) * 2019-11-29 2021-11-02 新华三技术有限公司 Performance data transmission method and device
CN111177626A (en) * 2019-12-26 2020-05-19 北京达佳互联信息技术有限公司 Data transmission method, device and equipment
CN111901437B (en) * 2020-08-04 2022-12-20 北京一起教育信息咨询有限责任公司 Message transmission method, device and system
CN112667180B (en) * 2020-12-29 2024-05-28 百果园技术(新加坡)有限公司 Service data display method and device, computer equipment and storage medium
CN114418771B (en) * 2022-03-28 2022-08-09 深圳希施玛数据科技有限公司 Data transmission method and related device
CN115379013A (en) * 2022-06-29 2022-11-22 广州博冠信息科技有限公司 Data processing method and device and electronic equipment

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101079895A (en) * 2006-12-21 2007-11-28 腾讯科技(深圳)有限公司 A method, system and proxy service device for quick access to Web page

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101122921B (en) * 2007-09-21 2011-09-28 北京意科通信技术有限责任公司 Method forming tree-shaped display structure based on ajax and html
CN102456004B (en) * 2010-10-18 2014-04-02 金蝶软件(中国)有限公司 Query control method and system of page data
CN102982137A (en) * 2012-11-16 2013-03-20 北京百度网讯科技有限公司 Method and system and device for resource searching
CN106202549A (en) * 2016-07-26 2016-12-07 珠海市魅族科技有限公司 The method and device that a kind of picture loads
CN106254225A (en) * 2016-09-08 2016-12-21 乐视控股(北京)有限公司 E-mail messages display packing and Mail Clients

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101079895A (en) * 2006-12-21 2007-11-28 腾讯科技(深圳)有限公司 A method, system and proxy service device for quick access to Web page

Also Published As

Publication number Publication date
CN108259533A (en) 2018-07-06

Similar Documents

Publication Publication Date Title
CN108259533B (en) Data transmission method and device
CN105787077B (en) Data synchronization method and device
CN107943840B (en) Data processing method, system and computer readable storage medium
CN105451087A (en) Pushing method, terminals, historical data server and system for barrage information
CN110377440B (en) Information processing method and device
CN109150929B (en) Data request processing method and device under high concurrency scene
CN110717119A (en) Page jump method and device, electronic equipment and storage medium
CN111625308B (en) Information display method and device and electronic equipment
CN111784318A (en) Data processing method and device, electronic equipment and storage medium
CN111552712A (en) Report data extraction method and device and computer equipment
CN115114044A (en) Message pushing method, device, equipment and medium
CN110661851A (en) Data exchange method and device
CN109561048B (en) Communication management method and device
CN112732652A (en) Information display method and device and electronic equipment
CA3047069C (en) Highly scalable event brokering and audit traceability system
CN108667647B (en) Method and device for setting device parameters and server
CN116541591A (en) Information processing method, device, electronic equipment and storage medium
CN112445861A (en) Information processing method, device, system and storage medium
CN110928895A (en) Data query method, data table establishing method, device and equipment
CN110545296A (en) Log data acquisition method, device and equipment
CN115454666A (en) Data synchronization method and device among message queue clusters
CN111479142B (en) Program content updating method and system based on information release
CA3216523A1 (en) Multi-factor routing system for exchanging business transactions
CN111506644B (en) Application data processing method and device and electronic equipment
CN109447293B (en) Product data processing method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1257327

Country of ref document: HK

GR01 Patent grant
GR01 Patent grant