Method, device, terminal, server and storage medium of processing network request and response

• US 10,574,773 B2
• Filed: 04/07/2017
• Issued: 02/25/2020
• Est. Priority Date: 07/20/2016
• Status: Active Grant

• Current Assignee: Ping An Technology Company Limited (Ping An Insurance (Group) Company of China, Ltd.)
• Original Assignee: Ping An Technology Company Limited (Ping An Insurance (Group) Company of China, Ltd.)
• Inventors: Xiang, Yangjun
• Primary Examiner(s): Walsh, John B
• Application Number:
  US15/579,266
• Publication Number:
  US 20180309842A1
• Time in Patent Office: 1,054 Days
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1074 for supporting data block transmission mechanisms file transfer H04L67/06
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing

Abstract

A method of processing a network request and response includes: merging a plurality of requests to obtain a merged request; transmitting the merged request to a server side; detecting a current status identification of the merged request; when the status indicated by the current status identification shows that data is transferring, receiving resource data corresponding to each request in the merged request and returned by the server side, and detecting the received resource data and obtaining a boundary identification contained in the received resource data; extracting and processing the resource data corresponding to each request in the merged request one by one according to the obtained boundary identification; and when the status indicated by the current status identification shows that the data transferring is completed, stopping receiving the resource data.

Claims

1. A method of processing a network request and response, comprising:

merging a plurality of HTTP resource requests to obtain a merged request;

transmitting the merged request to a server side;

detecting a current status identification of the merged request;

receiving, when the status indicated by the current status identification shows that data is transferring, receiving resource data corresponding to each request in the merged request and returned by the server side;

first obtaining a first boundary identification contained in the received resource data, the first boundary identification identifying that complete resource data responsive to a first HTTP resource request in the merged request has been successfully received;

first extracting and processing the HTTP resource data corresponding to the first HTTP request in the merged request according to the obtained boundary identification; and

stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed;

wherein the first extracting and processing begins before receipt of all of the complete resource data for all of the HTTP requests of the merged request.

2. The method of claim 1, wherein after stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed, the method further comprises:

extracting and processing the resource data received after the last obtained boundary identification.

3. The method of claim 1, wherein the merging the plurality of requests to obtain the merged request comprises:

merging requests which request for resource data with the same type in a preset manner to obtain the merged request, wherein the preset manner can be that predefining a separator to separate resources data requested by different requests.

4. The method of claim 1, wherein the boundary identification is configured to identify the resource data uniquely, and the boundary identification can comprises a time stamp and a separator line.

5. The method of claim 1, wherein the stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed comprises:

receiving a message segment with an end mark, wherein the status indicated by the current status identification of the merged request shows that the data transferring is completed, and

closing a connection with the server side.

6. The method of claim 1, further comprising:

second obtaining, after the first obtaining, a second boundary identification contained in the received resource data, the second boundary identification identifying that complete resource data responsive to a second HTTP resource request in the merged request has been successfully received; and

second extracting and processing, the HTTP resource data corresponding to the second HTTP resource request in the merged request according to the obtained boundary identification;

wherein the second extracting and processing begins after commencement of the first extracting and processing and before receipt of all of the complete resource data for all of the requests of the merged request.

7. A terminal comprising a processor, and a memory storing computer executable instructions, which, when executed by the processor cause the processor to perform steps comprising:

merging a plurality of HTTP resource requests to obtain a merged request;

transmitting the merged request to a server;

detecting a current status identification of the merged request;

receiving, when the status indicated by the current status identification shows that data is transferring, receiving resource data returned by the server and corresponding to each request in the merged request;

first obtaining a first boundary identification contained in the received resource data, the first boundary identification identifying that complete resource data responsive to a first HTTP resource request in the merged request has been successfully received;

first extracting and processing the HTTP resource data corresponding to the first request in the merged request according to the obtained boundary identification; and

stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed;

wherein the first extracting and processing begins before receipt of all of the complete resource data for all of the HTTP requests of the merged request.

8. The terminal of claim 7, wherein the computer executable instructions, which, when executed by the processor, cause the processor to perform steps comprising:

after step of stopping receiving the resource when the status indicated by the current status identification shows that the data transferring is completed, extracting and processing the resource data received after the last obtained boundary identification.

9. The terminal of claim 7, wherein the merging the plurality of requests to obtain the merged request comprises:

merging requests which request for resource data with the same type in a preset manner to obtain the merged request, wherein the preset manner can be that predefining a separator to separate resources data requested by different requests.

10. The terminal of claim 7, wherein the boundary identification is configured to identify the resource data uniquely, and the boundary identification can comprises a time stamp and a separator line.

11. The terminal of claim 7, wherein the stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed comprises:

receiving a message segment with an end mark, wherein the status indicated by the current status identification of the merged request shows that the data transferring is completed, and

closing a connection with the server side.

12. The terminal of claim 7, the steps further comprising:

second obtaining, after the first obtaining, a second boundary identification contained in the received resource data, the second boundary identification identifying that complete resource data responsive to a second HTTP resource request in the merged request has been successfully received; and

second extracting and processing, the HTTP resource data corresponding to the second HTTP resource request in the merged request according to the obtained boundary identification;

wherein the second extracting and processing begins after commencement of the first extracting and processing and before receipt of all of the complete resource data for all of the requests of the merged request.

13. At least one non-transitory computer-readable medium comprising computer executable instructions, which, when executed by at least one processor cause the at least one processor to perform steps comprising:

merging a plurality of HTTP resource requests to obtain a merged request;

transmitting the merged request to a server;

detecting a current status identification of the merged request;

receiving, when the status indicated by the current status identification shows that data is transferring, receiving resource data returned by the server and corresponding to each request in the merged request;

first obtaining a first boundary identification contained in the received resource data, the first boundary identification identifying that complete resource data responsive to a first HTTP resource request in the merged request has been successfully received;

first extracting and processing the HTTP resource data corresponding to the first HTTP request in the merged request one by one according to the obtained boundary identification; and

stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed;

wherein the first extracting and processing begins before receipt of all of the complete resource data for all of the HTTP requests of the merged request.

14. The non-transitory computer-readable medium of claim 13, wherein the computer executable instructions, which, when executed by the at least one processor, cause the at least one processor to perform steps comprising:

after step of stopping receiving the resource when the status indicated by the current status identification shows that the data transferring is completed, extracting and processing the resource data received after the last obtained boundary identification.

15. The non-transitory computer-readable medium of claim 13, wherein the merging the plurality of requests to obtain the merged request comprises:

merging requests which request for resource data with the same type in a preset manner to obtain the merged request, wherein the preset manner can be that predefining a separator to separate resources data requested by different requests.

16. The non-transitory computer-readable medium of claim 13, wherein the boundary identification is configured to identify the resource data uniquely, and the boundary identification can comprises a time stamp and a separator line.

17. The non-transitory computer-readable medium of claim 13, wherein the stopping receiving the resource data, when the status indicated by the current status identification shows that the data transferring is completed comprises:

receiving a message segment with an end mark, wherein the status indicated by the current status identification of the merged request shows that the data transferring is completed, and

closing a connection with the server side.

18. The media of claim 13, the steps further comprising:

second obtaining, after the first obtaining, a second boundary identification contained in the received resource data, the second boundary identification identifying that complete resource data responsive to a second HTTP resource request in the merged request has been successfully received; and

second extracting and processing, the HTTP resource data corresponding to the second HTTP resource request in the merged request according to the obtained boundary identification;

wherein the second extracting and processing begins after commencement of the first extracting and processing and before receipt of all of the complete resource data for all of the requests of the merged request.