You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gossip.apache.org by "Edward Capriolo (JIRA)" <ji...@apache.org> on 2017/02/13 16:54:41 UTC
[jira] [Updated] (GOSSIP-56) GossipCore should allow registration
of handlers
[ https://issues.apache.org/jira/browse/GOSSIP-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated GOSSIP-56:
----------------------------------
Description:
Currently GossipCore is a case statement. It would be better if we registered handlers. This would allows users to extend the protocol.
# We need a hashmap of Class -> Handler
# When GossipCore.receive(Base message) gets a message it gets the class of the message and looks it up in the hashmap
# Builder class allows users to specify other handlers
# Common handlers are enabled by default
was:Currently GossipCore is a case statement. It would be better if we registered handlers. IE if message instanceof X handle with Y.
> GossipCore should allow registration of handlers
> ------------------------------------------------
>
> Key: GOSSIP-56
> URL: https://issues.apache.org/jira/browse/GOSSIP-56
> Project: Gossip
> Issue Type: New Feature
> Reporter: Edward Capriolo
>
> Currently GossipCore is a case statement. It would be better if we registered handlers. This would allows users to extend the protocol.
> # We need a hashmap of Class -> Handler
> # When GossipCore.receive(Base message) gets a message it gets the class of the message and looks it up in the hashmap
> # Builder class allows users to specify other handlers
> # Common handlers are enabled by default
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)