curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cammckenzie <...@git.apache.org>
Subject [GitHub] curator pull request: CURATOR-173
Date Sat, 21 Feb 2015 03:51:10 GMT
Github user cammckenzie commented on the pull request:

    https://github.com/apache/curator/pull/67#issuecomment-75354182
  
    I've had a brief look at this, and I think it looks ok.
    A quick thought about allowing for dynamic change to the schema, is it better to get the
lock implementation instance to return a reference to an instance of the LockSchema object
that is specific to that particular lock instance? The lock implementation could then update
this reference with any dynamic content?
    
    Obviously  this would add the need for synchronisation etc.


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