Synchronizing Network Feeds in High-Frequency Network Events

• US 20100063995A1
• Filed: 09/09/2008
• Published: 03/11/2010
• Est. Priority Date: 09/09/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Chen, Benson Kwuan-Yi, Wrobel, Anthony William JR., Moore, Victor S., Gilfix, Michael
• Granted Patent: US 8,924,650 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

A cache server receives a request from a client that includes a requesting entity tag. In turn, the cache server extracts a starting identifier and an ending identifier from the requesting entity tag. The starting identifier is associated with a starting entry and the ending identifier is associated with an ending entry. Next, the cache server determines whether a subsequent entity tag exists that includes a subsequent starting identifier that matches the requesting entity tag'"'"'s ending identifier. When the cache server identifies a subsequent entity tag, the cache server sends the subsequent entity tag and one or more update entries corresponding to the subsequent entity tag to the client.

Claims

1. A machine-implemented method comprising:

receiving a request from a client, the request including a requesting entity tag;

extracting a starting identifier and an ending identifier from the requesting entity tag, the starting identifier associated with a starting entry and the ending identifier associated with an ending entry;

determining whether a subsequent entity tag exists that includes a subsequent starting identifier that matches the requesting entity tag'"'"'s ending identifier;

in response to determining that the subsequent entity tag exists that includes the subsequent starting identifier matching the requesting entity tag'"'"'s ending identifier, sending the subsequent entity tag and one or more update entries to the client, the update entries corresponding to the subsequent entity tag.

2. The method of claim 1 further comprising:

in response to determining that the subsequent entity tag does not exist, determining whether a duplicate entity tag exists that includes a duplicate starting identifier and a duplicate ending identifier, wherein the duplicate starting identifier matches the starting identifier and the duplicate ending identifier matches the ending identifier;

in response to determining that the duplicate entity tag exists, sending a no content response to the client.

3. The method of claim 2 further comprising:

in response to determining that the duplicate entity tag does not exist, sending a request to a feed server, wherein the request includes the requesting entity tag;

receiving a response from the feed server, wherein the response includes a new entity tag and one or more corresponding new update entries, the new entity tag including a new starting identifier and a new ending identifier; and

sending the new entity tag and the one or more new update entries to the client.

4. The method of claim 3 wherein the new starting identifier matches the ending identifier.

5. The method of claim 3 further comprising:

storing the new entity tag and the one or more new update entries in a repository; and

providing the new entity tag and the one or more new update entries to a different client.

6. The method of claim 1 wherein the one or more update entries comprise entries occurring after the ending entry through a subsequent entry corresponding to the subsequent ending identifier.

7. The method of claim 1 further comprising:

wherein the client is adapted to update a web feed using the subsequent entries; and

wherein the client is adapted to include the responding entity tag in a subsequent request.

8. An information handling system comprising:

one or more processors;

a memory accessible by at least one of the processors;

a nonvolatile storage area accessible by at least one of the processors;

a set of instructions stored in the memory and executed by at least one of the processors in order to perform actions of;

receiving a request from a client, the request including a requesting entity tag;

extracting a starting identifier and an ending identifier from the requesting entity tag, the starting identifier associated with a starting entry and the ending identifier associated with an ending entry;

determining whether a subsequent entity tag exists that includes a subsequent starting identifier that matches the requesting entity tag'"'"'s ending identifier;

in response to determining that the subsequent entity tag exists that includes the subsequent starting identifier matching the requesting entity tag'"'"'s ending identifier, sending the subsequent entity tag and one or more update entries to the client, the update entries corresponding to the subsequent entity tag.

9. The information handling system of claim 8 wherein the set of instructions performs actions of:

in response to determining that the subsequent entity tag does not exist, determining whether a duplicate entity tag exists that includes a duplicate starting identifier and a duplicate ending identifier, wherein the duplicate

starting identifier matches the starting identifier and the duplicate ending identifier matches the ending identifier;

in response to determining that the duplicate entity tag exists, sending a no content response to the client.

10. The information handling system of claim 9 wherein the set of instructions performs actions of:

in response to determining that the duplicate entity tag does not exist, sending a request to a feed server, wherein the request includes the requesting entity tag;

receiving a response from the feed server, wherein the response includes a new entity tag and one or more corresponding new update entries, the new entity tag including a new starting identifier and a new ending identifier; and

sending the new entity tag and the one or more new update entries to the client.

11. The information handling system of claim 10 wherein the new starting identifier matches the ending identifier.

12. The information handling system of claim 10 wherein the set of instructions performs actions of:

storing the new entity tag and the one or more new update entries in a repository; and

providing the new entity tag and the one or more new update entries to a different client.

13. The information handling system of claim 8 wherein the one or more update entries comprise entries occurring after the ending entry through a subsequent entry corresponding to the subsequent ending identifier.

14. A computer program product stored in a computer readable medium, comprising functional descriptive material that, when executed by an information handling system, causes the information handling system to perform actions that include:

receiving a request from a client, the request including a requesting entity tag;

extracting a starting identifier and an ending identifier from the requesting entity tag, the starting identifier associated with a starting entry and the ending identifier associated with an ending entry;

determining whether a subsequent entity tag exists that includes a subsequent starting identifier that matches the requesting entity tag'"'"'s ending identifier;

in response to determining that the subsequent entity tag exists that includes the subsequent starting identifier matching the requesting entity tag'"'"'s ending identifier, sending the subsequent entity tag and one or more update entries to the client, the update entries corresponding to the subsequent entity tag.

15. The computer program product of claim 14 wherein the information handling system further performs actions that include:

in response to determining that the subsequent entity tag does not exist, determining whether a duplicate entity tag exists that includes a duplicate starting identifier and a duplicate ending identifier, wherein the duplicate starting identifier matches the starting identifier and the duplicate ending identifier matches the ending identifier;

in response to determining that the duplicate entity tag exists, sending a no content response to the client.

16. The computer program product of claim 15 wherein the information handling system further performs actions that include:

in response to determining that the duplicate entity tag does not exist, sending a request to a feed server, wherein the request includes the requesting entity tag;

receiving a response from the feed server, wherein the response includes a new entity tag and one or more corresponding new update entries, the new entity tag including a new starting identifier and a new ending identifier; and

sending the new entity tag and the one or more new update entries to the client.

17. The computer program product of claim 16 wherein the new starting identifier matches the ending identifier.

18. The computer program product of claim 16 wherein the information handling system further performs actions that include:

storing the new entity tag and the one or more new update entries in a repository; and

providing the new entity tag and the one or more new update entries to a different client.

19. The computer program product of claim 14 wherein the one or more update entries comprise entries occurring after the ending entry through a subsequent entry corresponding to the subsequent ending identifier.

20. The computer program product of claim 14 wherein the information handling system further performs actions that include:

wherein the client is adapted to update a web feed using the subsequent entries; and

wherein the client is adapted to include the responding entity tag in a subsequent request.