You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gossip.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/03 18:30:00 UTC

[jira] [Commented] (GOSSIP-75) Voting interface

    [ https://issues.apache.org/jira/browse/GOSSIP-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151902#comment-16151902 ] 

ASF GitHub Bot commented on GOSSIP-75:
--------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-gossip/pull/62


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