Doug Cutting commented on ZOOKEEPER-78:

The project's patch submission mechanism is not inflexible, but neither should 
it be changed unilaterally on an issue-by-issue basis.  The currently 
acceptable mechanism is to attach patch files to Jira, generated by 'svn diff'. 
 When files are renamed, a shell script should be provided that performs the 
renames, where the script is run before the patch is applied.  If some find 
this awkward, then a separate discussion should be launched on the mailing 
list.  Some projects are now, e.g., using 'git' to handle things like this, but 
this needs to be done carefully so that the entire community is included in the 
process.  Fewer, simpler mechanisms generally include more people.

> added a high level protocol/feature - for easy Leader Election or exclusive 
> Write Lock creation
> -----------------------------------------------------------------------------------------------
>                 Key: ZOOKEEPER-78
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-78
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: java client
>    Affects Versions: 3.0.0
>            Reporter: james strachan
>         Attachments: patch_with_including_Benjamin's_fix.patch, 
> using_zookeeper_facade.patch
> Here's a patch which adds a little WriteLock helper class for performing 
> leader elections or creating exclusive locks in some directory znode. Note 
> its an early cut; am sure we can improve it over time. The aim is to avoid 
> folks having to use the low level ZK stuff but provide a simpler high level 
> abstraction.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to