curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gtully <...@git.apache.org>
Subject [GitHub] curator issue #161: CURATOR-344 - limit shared value watcher to valid change...
Date Tue, 30 Aug 2016 12:49:30 GMT
Github user gtully commented on the issue:

    https://github.com/apache/curator/pull/161
  
    thanks for the feedback.
    I fixed up the unit test to make it more deterministic.
    Changed the watcher to do an update and notification in the background.
    That sorts my use case however the update events should only fire on valid change events.
    Added additional unit test to track change events between disconnect and reconnect and
made the matching change to restrict the callback to valid change events.
    I think it is better on both counts.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message