[
https://issues.apache.org/jira/browse/IGNITE-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328760#comment-15328760
]
Andrey Kornev commented on IGNITE-3306:
---------------------------------------
Maybe we do not need to expose {{setCustomEventListener(...)}} at all, as the
custom events may be subscribed to using the standard
{{IgniteEvents.localListen(lsnr, EVT_MY_CUSTOM_DISCO_EVENT)}}, which makes more
sense as this way the discovery events would be delivered in total order.
Also, maybe we could improve the naming and do not call it "custom discovery
messages" on the public API level.
> Extend IgniteCluster interface with the methods to send and receive custom
> discovery events
> -------------------------------------------------------------------------------------------
>
> Key: IGNITE-3306
> URL: https://issues.apache.org/jira/browse/IGNITE-3306
> Project: Ignite
> Issue Type: Improvement
> Reporter: Andrey Kornev
>
> {{GridDiscoveryManager}} already provides the methods for sending/receiving
> custom discovery messages: {{GridDiscoveryManager.sendCustomEvent(...)}} and
> {{GridDiscoveryManager.setCustomEventListener(...)}} methods correspondingly.
> This API is very powerful as it provides reliable delivery guarantees that
> are totally ordered with respect to the rest of discovery events. It's
> essential for implementing so-called view-synchronous group communication
> primitives.
> Unfortunately, {{GridDiscoveryManager}} is not part of the public API.
> This ticket proposes to extend {{IgniteCluster}} interface to expose those
> methods. {{DiscoveryCustomMessage}} class should also be moved out of the
> {{internal}} package to a public package.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
