[
https://issues.apache.org/jira/browse/S4-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Morel updated S4-37:
-----------------------------
Fix Version/s: (was: 0.6)
0.7
rescheduling for a future release
> Emitters should allow registering a callback
> --------------------------------------------
>
> Key: S4-37
> URL: https://issues.apache.org/jira/browse/S4-37
> Project: Apache S4
> Issue Type: New Feature
> Affects Versions: 0.5.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Fix For: 0.7
>
>
> In the current state, emitters (udp, tcp, and others) send the messages
> across. They do not necessarily acknowledge the information regarding the
> send (success/failure) to the calling layer.
> An ACK from the emitter is important to realize more complicated
> emitter/listener protocols. For instance, to implement a ReplicationEmitter
> (the message is sent to multiple nodes instead of one node, say for
> fault-tolerance), the message should be processed only after it is replicated
> the required number of times. So, if we are using TCP as the underlying
> layer, it should callback when the operation succeeds.
> I am eager to hear comments on (1) should we provision for complicated
> protocols? (2) if so, is there any better way of going about things?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
