[
https://issues.apache.org/jira/browse/KAFKA-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-398.
-----------------------------
Resolution: Won't Fix
> Enhance SocketServer to Enable Sending Requests
> -----------------------------------------------
>
> Key: KAFKA-398
> URL: https://issues.apache.org/jira/browse/KAFKA-398
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8.1
> Reporter: Guozhang Wang
> Labels: features
> Attachments: kafka-398-0.7-v1.patch, kafka-398-0.7-v2.patch
>
>
> Currently the SocketServer is only used for reactively receiving requests and
> send responses but not used for pro-actively send requests and receive
> responses. Hence it does not need to remember which channel/key correspond to
> which consumer.
> On the other hand, there are cases such as consumer coordinator that needs
> SocketServer to send requests and receive responses to the consumers.
> It would be nice to add this functionality such that an API can be called
> with the id string and the request message, and the SocketServer will figure
> out which channel to use and write that message to the key's attachment and
> set the flag as WRITABLE so that the processor can then send it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
