Customizing posts by activity type and client type
View Patent ↗A system and method for per-client, per-type customizations to posts in an activity stream comprises an extraction pipeline and a rendering pipeline. The extraction pipeline can include a library of embedded code, data type taxonomy and an embed converter. The data type taxonomy is coupled to an activity source to receive activity information, and to produce a first protocol buffer. The embed converter produces a type-specific protocol buffer from the first protocol buffer and embedded code based in part upon the type of activity and the type of client. The type-specific protocol buffer is provided to the client to process activity information or present activity information. The disclosure also includes a method for processing a post in an activity stream on a per-client, per-type basis.
1. A computer-implemented method for processing posts in activity streams, comprising:
receiving, with one or more computing devices, a client type specifying a type of a client device;
receiving, with the one or more computing devices, activity information from an activity source;
receiving, with the one or more computing devices, an activity type;
creating, with the one or more computing devices, a first protocol buffer using the activity type and the activity information;
selecting, with the one or more computing devices, embedded code from a library of embedded code based in part upon the client type and the activity type;
adding, with the one or more computing devices, the embedded code to the first protocol buffer to create a second protocol buffer; and
sending, with the one or more computing devices, the second protocol buffer for rendering of the activity information.
2. The method of claim 1 further comprising storing, with the one or more computing devices, the first protocol buffer at an extraction pipeline.
3. The method of claim 1 wherein creating the first protocol buffer also uses the client type to determine the first protocol buffer.
4. The method of claim 1 wherein the first protocol buffer is a generic schema.org protocol buffer.
5. The method of claim 1 further comprising storing, with the one or more computing devices, the second protocol buffer at an extraction pipeline.
6. The method of claim 1 wherein the second protocol buffer is a type-specific protocol buffer.
7. The method of claim 1 wherein the embedded code includes a type-specific protocol buffer, Java, JavaScript, one or more custom templates, and custom styling.
8. The method of claim 1 wherein the first protocol buffer is a serialization format with an interface description language.
9. A computer program product comprising a non-transitory computer usable medium including a computer readable program, wherein the computer readable program when executed on a computer causes the computer to:
receive a client type specifying a type of a client device;
receive activity information from an activity source;
receive an activity type;
create a first protocol buffer using the activity type and the activity information;
select embedded code from a library of embedded code based in part upon the client type and the activity type;
add the embedded code to the first protocol buffer to create a second protocol buffer; and
send the second protocol buffer for rendering of the activity information.
10. The computer program product of claim 9 , wherein the computer readable program when executed on the computer also causes the computer to store the first protocol buffer at an extraction pipeline.
11. The computer program product of claim 9 , wherein the client type is used to determine the first protocol buffer.
12. The computer program product of claim 9 , wherein the first protocol buffer is a generic schema.org protocol buffer.
13. The computer program product of claim 9 , wherein the computer readable program when executed on the computer also causes the computer to store the second protocol buffer at an extraction pipeline.
14. The computer program product of claim 9 , wherein the second protocol buffer is a type-specific protocol buffer.
15. The computer program product of claim 9 , wherein the embedded code includes a type-specific protocol buffer, Java, JavaScript, one or more custom templates, and custom styling.
16. The computer program product of claim 9 , wherein the first protocol buffer is a serialization format with an interface description language.
17. A computer-implemented method for processing posts in an activity stream, executing on one or more computing devices, the method comprising:
receiving, with the one or more computing devices, a client type specifying a type of a client device;
receiving, with the one or more computing devices, an activity type;
receiving, with the one or more computing devices, activity information from the client device;
creating, with the one or more computing devices, a type-specific protocol buffer based in part upon the client type and the activity type;
select embedded code from a library of embedded code based in part upon the client type and the activity type:
converting, with the one or more computing devices, the type-specific protocol buffer to a generic protocol buffer using the selected embedded code; and
sending, with the one or more computing devices, the generic protocol buffer to an activity source, the activity source being different from the client device.
18. The method of claim 17 wherein the activity type is a post of information.
19. The method of claim 17 wherein the generic protocol buffer is a generic schema.org protocol buffer.
20. A system for processing posts in an activity stream, the system comprising:
one or more processors;
the one or more processors being configured to:
receive a client type specifying a type of a client device;
receive activity information from an activity source;
receive an activity type;
create a first protocol buffer using the activity type and the activity information;
select embedded code from a library of embedded code based in part upon the client type and the activity type;
add the embedded code to the first protocol buffer to create a type-specific protocol buffer; and
send the type-specific protocol buffer to the client device for rendering of the activity information.
21. The system of claim 20 , wherein the activity source is one or more from a group of a social network server, a third party server, a micro-blogging server, a profile server, a SMS/MMS server, an IM server, a search server and a web server.
22. The system of claim 20 , wherein the embedded code includes an associated script, and a data map with associations between data and fields.
23. The system of claim 20 , wherein the embedded code is retrieved from a library of embedded code, and the library of embedded code includes a plurality of customized embedded codes, each of the customized embedded codes for processing information related to a specific activity type.
24. The system of claim 20 , wherein the one or more processors are further configured to communicate with the activity source and provide activity information to a data type taxonomy.
25. The system of claim 20 , wherein the one or more processors are further configured to communicate with the client device and determine the client type.