[
https://issues.apache.org/jira/browse/S4-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175650#comment-13175650
]
Karthik Kambatla commented on S4-37:
------------------------------------
Yes, all of this happens in the comm layer. But, we might want to support more
complicated protocols in the comm layer which themselves might use things like
UDP and TCP.
So, I guess I am asking for simple protocols like TCP to support callbacks and
not all Emitters. But, I am not sure how we can enforce such a thing on
particular emitters.
> 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
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Fix For: 0.5
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
