HTTP request pipeline optimization

• US 9,311,424 B2
• Filed: 05/17/2012
• Issued: 04/12/2016
• Est. Priority Date: 05/17/2012
• Status: Expired due to Fees

• Current Assignee: Qualcomm Innovation Center Incorporated (Qualcomm, Inc.)
• Original Assignee: Qualcomm, Inc.
• Inventors: Sekhar, Vivek
• Primary Examiner(s): Tran, Jimmy H
• Application Number:
  US13/474,486
• Publication Number:
  US 20130311601A1
• Time in Patent Office: 1,426 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: H04L 1/0052 Realisations of complexity reduction techniques, e.g. pipelining or use of look-up tables
• CPC Class Codes: H04L 49/1546 using pipelined operation
• CPC Class Codes: H04L 49/3063 Pipelined operation

Abstract

A computing device comprising a transmitter/receiver adapted to communicate with a network and an application adapted to send a plurality of object requests through the transmitter/receiver, wherein, the plurality of object requests are placed in an order dependent upon at least one of an object size and an object type.

Claims

1. A client computing device comprising,

a hardware transmitter/receiver adapted to communicate with a network;

an application within a web browser, comprising program instructions stored on a memory and executed by a hardware processor on the client computing device, adapted to;

send a plurality of first HTTP HEAD object requests through a first socket of the web browser, via the transmitter/receiver,

receive information at the client computing device regarding at least one of an object size and an object type for each of a plurality of objects,

place a plurality of second HTTP object requests in a pipelined order for sending from the first socket of the client computing device,

wherein, the plurality of second HTTP object requests comprise download requests, and are placed in a pipelined order dependent upon at least one of,

the object size; and

the object type.

2. The client computing device of claim 1 wherein,

the object type comprises at least one of,

at least one JavaScript,

at least one cascading style sheet, and

at least one image;

and

the order of the plurality of second HTTP object requests comprises,

a request for the at least one JavaScript before a request for the at least one cascading style sheet,

a request for the at least one cascading style sheet prior to a request for the image, and

a request for the image before a request for at least one video or audio file.

3. The client computing device of claim 2 wherein,

the at least one JavaScript and at least one cascading style sheet comprise,

at least one JavaScript and cascading style sheet having a first object size, and

at least one JavaScript and cascading style sheet having a second object size, wherein the second object size is greater than the first object size;

and

the order further comprises, a request for the at least one JavaScript and cascading style sheeting having a first object size before a request for the at least one JavaScript and cascading style sheet having a second object size.

4. The client computing device of claim 2 wherein,

the at least one image comprises a first image having a first image file size and a second image having a second image file size;

the second image file size is larger than the first image file size; and

the order further comprises a request for the first image before a request for the second image.

5. The client computing device of claim 1 further comprising a plurality of sockets;

and wherein,

the first socket has an upper threshold object size setting,

one or more responses to the plurality of first HTTP HEAD requests indicates that at least one first object has an object size under the upper threshold object size and at least one second object has an object size exceeding the upper threshold object size setting, and

one or more of the plurality of second HTTP object requests comprises a request for the first object via the first socket of the client computing device, and

one or more of the plurality of second HTTP object requests comprises a request for the second object via a second socket of the client computing device.

6. A client computing system comprising program instructions stored on memory and executed by a hardware processor, which cause the system to,

send a plurality of first HTTP HEAD requests from the client computing device to obtain a file size and type of one or more digital objects;

detect, at the client computing device, the file size and file type of the one or more digital objects for which the plurality of first HTTP HEAD requests were sent;

order a plurality of second HTTP requests to be sent from a first socket of the client computing device based on one or more of the file size and the file type;

set an upper threshold for a digital object size that may be requested via a second HTTP request on a first socket of the client computing device;

send at least one second HTTP request on a second socket of the client computing device for a digital object that exceeds the upper threshold for a digital object size.

7. The system of claim 6, wherein the upper threshold for a digital object size that may be requested via a second HTTP request on a first socket is configurable by an end user of a client device.

8. The system of claim 6 wherein,

the file type of the one or more digital objects comprises at least one

JavaScript,

cascading style sheet, and

image;

and wherein the system requests the at least one JavaScript and at least one cascading style sheet before requesting the at least one image.

9. A method to optimize pipelining of HTTP requests comprising,

determining, by sending a plurality of first HTTP HEAD requests from a client computing device, at least one of a file type and a file size of a plurality of digital objects;

grouping a plurality of second HTTP requests at the client computing device by at least one of the file type and the file size to be sent from a first socket, wherein the plurality of second HTTP object requests comprise download requests;

issuing one or more second HTTP requests for at least one first file type on the first socket of the client computing device; and

issuing one or more second HTTP requests for at least one second file type on a second socket of the client computing device.

10. The method of claim 9, further comprising,

receiving one or more first files comprising the at least one first file type;

and

receiving one or more second files comprising the at least one second file type.

11. The method of claim 9 wherein,

the at least one first file type comprises at least one of a JavaScript and a cascading style sheet;

and

the at least one second file type comprises an image.

12. A non-transitory, tangible computer readable storage medium, encoded with processor readable instructions to perform a method of optimize HTTP requests comprising,

determining, by sending a plurality of first HTTP HEAD requests from a client computing device, at least one of a file type and a file size of a plurality of digital objects;

grouping a plurality of second HTTP requests at the client computing device by at least one of the file type and the file size to be sent from a first socket, wherein the plurality of second HTTP object requests comprise download requests;

issuing one or more second HTTP requests for at least one first file type on the first socket of the client computing device; and

issuing one or more second HTTP requests for at least one second file type on a second socket of the client computing device.

13. The non-transitory, tangible computer readable storage medium of claim 12, further comprising, receiving the at least one file type object before receiving the at least one second file type object.

14. The non-transitory, tangible computer readable storage medium of claim 12, wherein,

sending a HTTP request for at least one first file type object comprises sending a plurality of HTTP requests for at least one first file type object;

and

the plurality of HTTP requests comprise,

a first HTTP request for a first file type object having a first file size, and

at least one second HTTP request for a second file type object having a second file size being sent after the first HTTP request, wherein the second file size is greater than the first file size.

15. The non-transitory, tangible computer readable storage medium of claim 12 wherein,

the at least one first file type object comprises a JavaScript and a cascading style sheet;

and

the at least one second file type object comprises an image.

16. The non-transitory, tangible computer readable storage medium of claim 12 wherein, the file type comprises the MIME type.