Synchronizing network feeds in high-frequency network events

• US 8,924,650 B2
• Filed: 09/09/2008
• Issued: 12/30/2014
• Est. Priority Date: 09/09/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Chen, Benson Kwuan-Yi, Gilfix, Michael, Moore, Victor S., Wrobel, Anthony William Jr.
• Primary Examiner(s): Algibhah, Hamza
• Assistant Examiner(s): COX, NATISHA D
• Application Number:
  US12/207,005
• Publication Number:
  US 20100063995A1
• Time in Patent Office: 2,303 Days
• Field of Search: 709/222
• US Class Current: 711/133
• 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 first entity tag that includes a first starting identifier and a first ending identifier, the first starting identifier associated with a starting entry and the first ending identifier associated with an ending entry;

selecting a second entity tag that corresponds to one or more update entries;

determining whether the second entity tag includes a second starting identifier that matches the first ending identifier included in the first entity tag; and

in response to determining that the second entity tag includes the second starting identifier that matches the first ending identifier, sending the second entity tag and one or more of the update entries to the client.

2. The method of claim 1 further comprising:

in response to determining that the second entity tag does not include the second starting identifier that matches the first ending identifier, determining whether a third entity tag includes a third starting identifier that matches the first starting identifier and includes a third ending identifier that matches the first ending identifier;

in response to determining that the third 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 third entity tag does not exist, sending a request to a feed server, wherein the request includes the first 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 first 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 second ending identifier.

7. The method of claim 1 further comprising:

wherein the client is adapted to update a web feed using the one or more update entries; and

wherein the client is adapted to include the second 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 first entity tag that includes a first starting identifier and a first ending identifier, the first starting identifier associated with a starting entry and the first ending identifier associated with an ending entry;

selecting a second entity tag that corresponds to one or more update entries;

determining whether the second entity tag includes a second starting identifier that matches the first ending identifier included in the first entity tag; and

in response to determining that the second entity tag includes the second starting identifier that matches the first ending identifier, sending the second entity tag and one or more of the update entries to the client.

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

in response to determining that the second entity tag does not include the second starting identifier that matches the first ending identifier, determining whether a third entity tag includes a third starting identifier that matches the first starting identifier and includes a third ending identifier that matches the first ending identifier;

in response to determining that the third 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 third entity tag does not exist, sending a request to a feed server, wherein the request includes the first 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 first 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 second ending identifier.

14. A computer program product stored on a non-transitory computer operable 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 first entity tag that includes a first starting identifier and a first ending identifier, the first starting identifier associated with a starting entry and the first ending identifier associated with an ending entry;

selecting a second entity tag that corresponds to one or more update entries;

determining whether the second entity tag includes a second starting identifier that matches the first ending identifier included in the first entity tag; and

in response to determining that the second entity tag includes the second starting identifier that matches the first ending identifier, sending the second entity tag and one or more of the update entries to the client.

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

in response to determining that the second entity tag does not include the second starting identifier that matches the first ending identifier, determining whether a third entity tag includes a third starting identifier that matches the first starting identifier and includes a third ending identifier that matches the first ending identifier;

in response to determining that the third 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 third entity tag does not exist, sending a request to a feed server, wherein the request includes the first 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 first 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 second 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 one or more update entries; and

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