[
https://issues.apache.org/jira/browse/GOSSIP-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088415#comment-16088415
]
ASF GitHub Bot commented on GOSSIP-75:
--------------------------------------
GitHub user Mirage20 opened a pull request:
https://github.com/apache/incubator-gossip/pull/62
[WIP] GOSSIP-75 Voting interface
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mirage20/incubator-gossip GOSSIP-75
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-gossip/pull/62.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #62
----
commit ecdaf721399ccb59362c8c8e3352c1cd5ee03c24
Author: Mirage Abeysekara <[email protected]>
Date: 2017-07-14T16:49:16Z
sample vote based lock
----
> Voting interface
> ----------------
>
> Key: GOSSIP-75
> URL: https://issues.apache.org/jira/browse/GOSSIP-75
> Project: Gossip
> Issue Type: New Feature
> Reporter: Edward Capriolo
>
> Gossip has CRDT support. This is an important building block to doing higher
> level things. The next piece is being able to act on an object when we
> receive it. For example lets take the most simple case. I want the cluster to
> vote on something such as "who asked for this lock first". Currently we
> replicate objects lazily through a thread, what we want to do is on reception
> of an object apply some function such that we can modify the object being
> received.
> The way I want to go about this is voting objects can be injected with a type
> like VoteContext
> http://stackoverflow.com/questions/27133161/how-to-pass-constructors-parameters-with-jackson
>
> Users can register Voter implementations. On receiving an object the
> interface allows logic to be run. In the case of a Voting each node appends
> its vote as the object moves around over time you can poll your local copy
> and determine the result of the vote.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
