Managing content for RSS alerts over a network

• US 20070100960A1
• Filed: 10/28/2005
• Published: 05/03/2007
• Est. Priority Date: 10/28/2005
• Status: Abandoned Application

• Current Assignee: Oath Inc. (Verizon Communications Inc.)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Cook, Michael, Pandey, Kamlesh, Matzanas, Sotirios, Eichstaedt, Matthias, Ludwig, Ronald, Swales, Stephen, Prishtina, Adam, Chen, Yunzhong
• Application Number:
  US11/262,503
• Publication Number:
  US 20070100960A1
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1006 with static server selection, e.g. the same server being selected for a specific client
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 67/1017 based on a round robin mechanism
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

A system, apparatus, and method are directed to managing an alert to a subscriber based on a change of content at an RSS content source (RCS). A content collector identifies changes in content from various RCSs. In one embodiment, the RCS may notify the content collector of a change in content. In another embodiment, a crawler is used to identify an RCS with changed content based, in part, on a subscriber'"'"'s request. Information about the RCS with changed content is provided to at least one of a plurality of matching engines using a load-balancing mechanism. Each of the matching engines manages a store that identifies subscribers that have requested an alert from a particular RCS. The matching engines further determine when the subscriber was last notified of a change in content from that RCS so that the subscriber is not notified multiple times of the same change.

Claims

1. A method of managing content for Really Simple Syndication (RSS) over a network, comprising:

determining content associated with an RSS feed;

determining an identifier for the RSS feed;

if a change is determined for content associated with the RSS feed, load balancing a determining of an association of the RSS feed to at least one of a plurality of subscribers based at least in part on the identifier; and

providing an RSS alert of the change in content to at least one subscriber that is associated with the RSS feed.

2. The method of claim 1, further comprising crawling the network to determine an availability of content associated with the RSS feed.

3. The method of claim 1, further comprising receiving a notification of content associated with the RSS feed.

4. The method of claim 1, wherein the load balancing further comprises performing load balancing actions based at least in part on one of round-robin, hops, latency, priority, bandwidth, capacity, RSS Content Source (RCS), identifier, RCS content type, subscriber, or type of delivery.

5. The method of claim 1, further comprising retrieving content for the RSS feed based on a search query.

6. The method of claim 1, further comprising determining if a subscriber is associated with the RSS feed based in part on at least one data structure having a key field and a value field, wherein the key field includes the identifier and the value field includes at least one other identifier for a particular subscriber.

7. The method of claim 1, further comprising providing the RSS alert if the change in content is unduplicated by other content previously associated with the RSS feed.

8. A system for managing content for Really Simple Syndication (RSS) over a network, comprising:

a collection component that is operative to perform actions, including;

determining content associated with an RSS feed;

determining an identifier associated with the RSS feed that is further associated with the determined content; and

a load balancer that is arranged to load balance the forwarding of the identifier to one of a plurality of match servers if a change in the content occurs,;

a match server that is arranged to receive the forwarded identifier and is operative to determine an association of the RSS feed with at least one subscriber based at least in part on the identifier; and

a delivery server that is arranged to forward an RSS alert to at least one subscriber that is determined to be associated with the RSS feed if content associated with the RSS feed is changed.

9. The system of claim 8, wherein the load balancer is arranged to perform load balancing actions based on at least one of round-robin, hops, latency, priority, bandwidth, capacity, RSS Content Source (RCS), identifier, content type, subscriber, or type of delivery.

10. The system of claim 8, further comprising determining an availability of content for the RSS feed based on at least one of receiving a notification associated with the RSS feed, or crawling the network for content associated with the RSS feed.

11. The system of claim 8, wherein the RSS alert is accessible to the subscriber with at least one of a personal computer, network appliance, or a mobile device.

12. The system of claim 8, wherein the collection component performs further actions including providing the identifier to the match server if content is unduplicated by other content previously associated with the RSS feed.

13. The system of claim 12, further comprises comparing a hash of at least a portion of the content to a hash of at least a portion of the other content to determine if the change in content is duplicative.

14. The system of claim 8, wherein the RSS alert is forwarded to the subscriber in at least one format, including, including email, Instant Messaging (IM), relay, chat, text message, Short Message Service (SMS), or Multi-media messaging.

15. A server that is operative to manage content for Really Simple Syndication (RSS) over a network, comprising:

a memory component for storing data;

a processing component for executing data that enables actions, including;

determining an availability of content associated with an RSS feed;

determining an identifier for the RSS feed;

if a change in content associated with the RSS feed is determined, load-balancing a determination for an association of the RSS feed to at least one of a plurality of subscribers based at least in part on the identifier; and

enabling an RSS alert to be provided to at least one subscriber that is associated with the RSS feed if the change in content occurred.

16. The server of claim 15, wherein the processing component enables further actions comprising:

comparing a first time period associated with RSS feed content to a second time period associated with other RSS feed content; and

if the first time period is more recent than the second time period, providing at least one indication that the change in content associated with the RSS feed occurred.

17. The server of claim 15, wherein the processing component enables further actions comprising determining if a subscriber is associated with the RSS feed based in part on a search for the identifier in a key field in at least one key-value pair for a plurality of key-value pairs.

18. The server of claim 15, wherein the RSS alert is forwarded to the subscriber in at least one format, including email, Instant Messaging (IM), relay, chat, text message, Short Message Service (SMS), or Multi-media messaging.

19. The server of claim 15, wherein the processing component performs further actions including enabling the RSS alert to be provided if the change in content is unduplicated by other content previously associated with the RSS feed.

20. A client that is operative for managing content for Really Simple Syndication (RSS) over a network, comprising:

a memory component for storing data; and

a processing component for executing data that enables actions, including;

enabling an RSS alert to be provided to at least one subscriber that is associated with an RSS feed; and

wherein the RSS alert indicates an occurrence of change in content associated with the RSS feed; and

wherein the association of the RSS feed to the at least one subscriber is load balanced based at least in part on an identifier that is determined to be associated with the RSS feed.

21. The client of claim 20, wherein the processing component performs further actions including enabling the RSS alert to be provided to the at least one subscriber if the change in content is unduplicated by other content previously associated with the RSS feed.

22. The client of claim 20, wherein the RSS alert is forwarded to the at least one subscriber in at least one format, including email, Instant Messaging (IM), relay, chat, text message, Short Message Service (SMS), or Multi-media messaging.

23. The client of claim 20, wherein the RSS alert is provided for access by the subscriber with at least one of a personal computer, network appliance, or a mobile device.

24. A processor readable medium that includes data, wherein the execution of the data provides for the management of RSS content over a network by enabling actions, including:

determining an availability of content associated with an RSS feed;

determining an identifier for the RSS feed;

if a change in content associated with the RSS feed is determined, load-balancing the determining of the association of the RSS feed to at least one of a plurality of subscribers based at least in part on the identifier; and

providing an RSS alert to at least one subscriber that is determined to be associated with the RSS feed if the change in content occurs.