CENTRALIZED FEED MANAGER

• US 20120166573A1
• Filed: 03/08/2012
• Published: 06/28/2012
• Est. Priority Date: 05/31/2001
• Status: Active Grant

• Current Assignee: R2 Solutions LLC (Acacia Research Corporation)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Athey, Kevin, Robison, John, Patel, Ashvinkumar P.
• Granted Patent: US 8,392,536 B2
• Time in Patent Office: Days
• US Class Current: 709/213
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

A method delivering content from a plurality of sources to a plurality of end servers through a central manager is provided. The method includes receiving the content from the plurality of sources at the central manager, formatting the content to a form usable by the plurality of end servers, creating a transaction generic to the plurality of end servers where the transaction includes a reference to a set of instructions for storing the formatted content, sending the transaction to an end server in the plurality of end servers, and calling the reference to execute the set of instructions where the set of instructions store the formatted content into the memory of the end server.

Claims

1-28. -28. (canceled)

29. A method of providing content, comprising:

receiving, by a processor, content streamed in a plurality of content types, each of the content types is streamed in a form different from other content types of the plurality of content types;

parsing, by the processor, the received content;

converting, by the processor, the received content into a generic form comprising a common format for the plurality of content types;

generating, by the processor, a transaction comprising at least a subset of the formatted content, the transaction is associated with one of the plurality of content types; and

transmitting, by the processor, the transaction to one or more content specific servers configured to forward the formatted content to a client device.

30. The method of claim 29, the generic form of the content is readable by a plurality of the content specific servers.

31. The method of claim 29, further comprising, receiving, at the processor, information regarding change of format of one of the plurality of content types.

32. The method of claim 31, further comprising, recognizing, by the processor, the changed format of the one content type.

33. The method of claim 32, further comprising, converting, by the processor, content of the changed format into the generic form comprising the common format for the plurality of content types.

34. The method of claim 29, further comprising, caching, by the processor, the transactions such that the cached transactions can be replayed to the content specific servers.

35. The method of claim 34, further comprising, eliminating, by the processor, unwanted content from the cached transactions.

36. The method of claim 34, the transactions are cached prior to the transmission to the content specific servers.

37. The method of claim 34, maintaining, by the processor, order of the cached transactions within each of the plurality of content types, the order is determined based on time stamps associated with the cached transactions.

38. A computing device comprising:

a processor;

a storage medium for tangibly storing thereon program logic for execution by the processor, the program logic comprising;

receiving logic, executed by the processor, for receiving content streamed in a plurality of content types, each of the content types is streamed in a form different from other content types of the plurality of content types;

parsing logic, executed by the processor, for parsing the received content;

converting logic, executed by the processor, for converting the received content into a generic form comprising a common format for the plurality content types;

generating logic, executed by the processor, for generating a transaction comprising at least a subset of the formatted content, the transaction is associated with one of the plurality of content types;

transmitting logic, executed by the processor, for transmitting the transaction to one or more content specific servers configured to forward the formatted content to a client device.

39. The system of claim 38, the generic form of the content is readable by a plurality of the content specific servers.

40. The system of 38, further comprising, at least one cache that caches transactions to be replayed to the content specific servers.

41. The system of claim 40, the cache is organized into three basic types assuming six different forms.

42. The system of claim 40, the cache is of default type that stores transactions sorted by the content type in a linear file with one file per specific content type.

43. The system of claim 42, a sports form of the cache is implemented on the default type, such that the sports form examines the transactions and stores the transactions.

44. The system of claim 40, the cache is of db type that stores actual transactions by appending each transaction to a value field based on a specific subject of the transaction.

45. The system of claim 44, a conversation form is implemented on the db type such that unwanted content is eliminated from the transactions and most recent transactions for a content type of the plurality of content types are stored, the most recent transactions are determined based on time stamps associated with the transactions.

46. A computer readable storage medium, having stored thereon, instructions which when executed by a processor, cause the processor to:

receive content streamed in a plurality of content types, each of the content types is streamed in a form different from other content types of the plurality of content types;

parse the received content;

convert the received content into a generic form comprising a common format for the plurality of content types;

generate a transaction comprising at least a subset of the formatted content, the transaction is associated with one of the plurality of content types; and

transmit the transaction to one or more content specific servers configured to forward the formatted content to a client device.

47. The medium of claim 46, the generic form of the content is readable by a plurality of the content specific servers.

48. The medium of claim 46, the processor further:

receives information regarding change of format of one of the plurality of content types;

recognizes the changed format of the content type; and

converts content of the changed format into the generic form comprising the common format for the plurality of content types.