HTTP-BASED CLIENT-SERVER COMMUNICATION SYSTEM AND METHOD

• US 20130086228A1
• Filed: 06/11/2010
• Published: 04/04/2013
• Est. Priority Date: 06/11/2010
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Goldman, Jason D.
• Application Number:
  US13/703,240
• Publication Number:
  US 20130086228A1
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: G06F 16/1787 Details of non-transparently synchronising file systems
• CPC Class Codes: G06F 16/95 Retrieval from the web
• 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]

Abstract

Systems and methods for robust, efficient, and secure client-server communication are provided. For example, one method of such client-server communication may involve receiving in the server a long polling HTTP request and a client status message, such as a file offer, via HTTP from the client. Such a file offer may indicate, for example, one or more files that are available for transfer from the client. Thereafter, the server may issue a command, such as a file request, as a response to the long polling HTTP request. Such a file request may request at least one of the one or more files that are available for transfer. There-after, the server may receive the at least one of the one or more files from the client via FTP.

Claims

1. A method comprising:

receiving, in a server, a long polling HTTP request from a client;

receiving, in the server, a file offer from the client via HTTP, wherein the file offer indicates one or more files that are available for transfer from the client;

issuing, from the server, a file request in response to the long polling HTTP request, wherein the file request requests at least one of the one or more files that are available for transfer; and

receiving, in the server, the at least one of the one or more files from the client via FTP.

2. The method of claim 1, wherein the file offer is received at a client-specific uniform resource locator (URL) that identifies the client.

3. The method of claim 1, comprising receiving, in the server, a confirmation message indicating that the at least one of the one or more files has been fully transferred at a client-specific uniform resource locator (URL) that identifies the client.

4. The method of claim 1, comprising determining, using the server, whether a confirmation message indicating that the at least one of the one or more files has been fully transferred has been received in the server from the client and, when the confirmation has been received, storing the at least one of the one or more files in the server.

5. The method of claim 1, comprising determining, using the server, whether a confirmation message indicating that the at least one of the one or more files has been transferred has been received in the server from the client and, when the confirmation has not been received, reissuing the file request from the server.

6. The method of claim 5, wherein determining whether the confirmation message has been received from the client is performed on a periodic basis.

7. The method of claim 5, wherein determining whether the confirmation message has been received from the client is performed after an amount of data has been received from the client, wherein the amount of data is estimated to equal a size of the at least one of the one or more files.

8. The method of claim 1, comprising determining, using the server, whether the one or more files that are available for transfer from the client should be requested and, when the one or more files are determined to be requested, adding the file request for the one or more files to a client queue that lists files for which future file requests are to be issued, wherein the file request is issued based at least in part on the client queue.

9. The method of claim 1, comprising determining, using the server, that network traffic or traffic to the client is beneath a threshold before issuing the file request.

10. The method of claim 1, comprising determining, using the server, that the client is not receiving a streamed file before issuing the file request.

11. A system comprising:

a client configured to initiate a long polling HTTP request, to communicate information regarding the client to a client-specific uniform resource locator via HTTP, and to receive a client-specific command in response to the long polling HTTP request; and

a server configured to receive the long polling HTTP request, to receive the information regarding the client at a client-specific uniform resource locator via HTTP, to generate the client-specific command based at least in part on the information regarding the client, and to communicate the client-specific command as a response to the long polling HTTP request.

12. The system of claim 11, wherein the information regarding the client comprises a file offer indicating one or more files available for transfer from the client and wherein the command comprises a file request that requests at least one of the one or more files.

13. The system of claim 11, comprising another client configured to initiate another long polling HTTP request, to communicate information regarding the other client to another client-specific uniform resource locator via HTTP, and to receive another client-specific command in response to the other long polling HTTP request;

wherein the server is configured to receive the other long polling HTTP request, to receive the information regarding the other client at the other client-specific uniform resource locator via HTTP, to generate the other client-specific command based at least in part on the information regarding the client, and to communicate the other client-specific command as a response to the long polling HTTP request.

14. A method comprising:

initiating a long polling HTTP request from a client to a server;

transmitting a file offer via HTTP from the client to the server, wherein the file offer indicates one or more files that are available for transfer from the client to the server;

receiving, in the client, a file request from the server in response to the long polling HTTP request, wherein the file request requests at least one of the one or more files that are available for transfer; and

transferring the at least one of the one or more files from the client to the server via FTP.

15. The method of claim 14, comprising determining, using the client, the file offer by collecting and packaging metadata associated with the one or more files that are available for transfer.