You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Dan Jemiolo (JIRA)" <ji...@apache.org> on 2006/07/28 21:16:14 UTC
[jira] Commented: (MUSE-44) Persistence of NotificationProducer and
SubscriptionManager entries
[ http://issues.apache.org/jira/browse/MUSE-44?page=comments#action_12424150 ]
Dan Jemiolo commented on MUSE-44:
---------------------------------
I have an implementation of this that is very similar to SG persistence, so hopefully test and validation of this can be done by end of the weekend.
> Persistence of NotificationProducer and SubscriptionManager entries
> -------------------------------------------------------------------
>
> Key: MUSE-44
> URL: http://issues.apache.org/jira/browse/MUSE-44
> Project: Muse
> Issue Type: New Feature
> Components: WSN NotificationProducer
> Affects Versions: 2.0.0 M1
> Reporter: Dan Jemiolo
> Assigned To: Dan Jemiolo
> Fix For: 2.0.0 M2
>
>
> Muse's router persistence records all the EPRs/resource instances, but the WSN impl still needs to save/reload all of the subscription data for each subscription resource. This should be the responsibility of each NotificationProducer impl - it should record its subscription data (EPR, consumer EPR, term time, etc) and then find the subscription (by EPR) upon reloading and assign all of its values back to pre-reboot state. This should require any change to the SubscriptionManager component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org