You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streams.apache.org by "Danny Sullivan (JIRA)" <ji...@apache.org> on 2013/08/01 20:37:48 UTC
[jira] [Commented] (STREAMS-19) create persistence layer to
maintain an on-going activity stream
[ https://issues.apache.org/jira/browse/STREAMS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726719#comment-13726719 ]
Danny Sullivan commented on STREAMS-19:
---------------------------------------
How about this idea: The repository layer would take the place in the camel context where the activityWarehouseDistributer is now (the distributeToSubscribers method). In place of the distributeToSubscribers method would be a repository service method that takes in the Exchange object, extracts the Activity Streams Java object from the body and stores it in the database. Then the distributeToSubscribers method would iterate through every subscriber (as it does now), make a call to the database according to the subscriber's filters, and add whatever activity objects are returned to the subscriber's stream array. This distributeToSubscribers method would then run on a timer (like every 60 seconds or so). This might make it harder for the database to be optional. Perhaps the distributeToSubscribers method can first check to see if there is a repository connection open, and if not turn to the activities queue?
> create persistence layer to maintain an on-going activity stream
> ----------------------------------------------------------------
>
> Key: STREAMS-19
> URL: https://issues.apache.org/jira/browse/STREAMS-19
> Project: Streams
> Issue Type: New Feature
> Reporter: Danny Sullivan
>
> Should be located in the architecture where the activity queue is located.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira