[
https://issues.apache.org/jira/browse/ZOOKEEPER-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChiaHung Lin updated ZOOKEEPER-935:
-----------------------------------
Status: Patch Available (was: Open)
According to the previous discussion
(http://mail-archives.apache.org/mod_mbox/hadoop-zookeeper-user/201005.mbox/%3c4bfd646c.2040...@apache.org%3e),
the patch containing sharedlock is created for concurrent primitive library
(http://wiki.apache.org/hadoop/ZooKeeper/SoC2010Ideas#Concurrent_Primitives_Library).
There is an issue I would like to discuss:
- sharelock source code indeed follows the way that WriteLock works, and its
default lock covers the WriteLock behaviour. These seems to me can be refactor
to e.g. use sharedlock only; however, I am not sure if this would semantic
correct.
I expect this patch may need more refinement before accepted; so I appreciate
any advice and suggestion.
Thanks.
> Concurrent primitives library - shared lock
> -------------------------------------------
>
> Key: ZOOKEEPER-935
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-935
> Project: Zookeeper
> Issue Type: Improvement
> Components: recipes
> Environment: Debian squeeze
> JDK 1.6.x
> zookeeper trunk
> Reporter: ChiaHung Lin
> Priority: Minor
> Attachments: ZOOKEEPER-935.patch
>
>
> I create this jira to add sharedock function. The function follows recipes at
> http://hadoop.apache.org/zookeeper/docs/r3.1.2/recipes.html#Shared+Locks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
