Difference between revisions of "Social Networking Library"
(→Architecture Scenario) |
(→Overview) |
||
Line 10: | Line 10: | ||
* Retrieving Users Feeds, Comments, Likes; | * Retrieving Users Feeds, Comments, Likes; | ||
* Managing Users Connections; | * Managing Users Connections; | ||
− | * | + | * Publishing Users Notifications; |
− | * Publishing Application | + | * Publishing Application News to User feeds. |
=== Architecture Scenario === | === Architecture Scenario === |
Revision as of 23:30, 13 December 2012
Overview
The purpose of this document is to provide instructions for developers wishing to exploit Social Networking from within their applications.
The gCube Social Library, so far, provides methods for:
- Publishing Users Posts;
- Retrieving Users Feeds, Comments, Likes;
- Managing Users Connections;
- Publishing Users Notifications;
- Publishing Application News to User feeds.
Architecture Scenario
The gCube Social Networking Library is the 'bridge' between your gCube Applications and the social networking facilities. The social networking facilities exploit a NoSQL data store for their storage. Specifically an Apache Cassandra data store. Figure 1 present the place of the Social Library in a simplified gCube Portal architecture.
How to use the gCube Social Networking Library (SNL)
Your gCube Application will the SNL through a specific ASL Extension, the ASL Social Extension
ASL Social Extension
The ASL Social Extension is formed by different modules, each of these is delegated to one specific task. Every module inherits from a super class called SocialPortalBridge. Currently there are two modules available:
- Application News Manager: to be used by gCube Applications when they need to post news on their user news feeds;
- User Notifications Manager: to be used by gCube Applications when they need to notify their users about some events.
The overall