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 Thu, 25 Aug 2016 16:03:43 GMT
Github user gtully commented on the issue:

    https://github.com/apache/curator/pull/161
  
    Thanks for taking the time to peek at this. I agree. 
    Doing everything async will make it a little heaver weight but I think it is more correct.

    There seems to be be some recipes that take executors, others that don't, but I have not
figured out if there is some pattern to this. Do you know?
    
    Short term, I can fix up the unit test to be deterministic (i.e. wait for connected).
    Maybe this can be tackled in two phases. The first making the watcher more discriminating.
For my use case, disconnecting is the important event.


---
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