[
https://issues.apache.org/jira/browse/THRIFT-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343233#comment-15343233
]
James E. King, III commented on THRIFT-3320:
--------------------------------------------
Seems like once we uncork two-way communcation where each side can set up
services in a multiplexed listener, and we ensure each end of the connection
has a proper endpoint, we could clean this up. One would expect both sides to
have multiple outstanding requests in flight. That said, I expect that each
request would have a unique request ID for that connection and as such we would
always be able to deliver the response to the request without knowing which
multiplexed service it belongs to. I did this in THRIFT-66, so I'm wondering
if we really need to include the service name in the response, since the
request ID should be unique for that session and that's enough to reliably
deliver the reply.
> TMessages of multiplexed service responses of should include service names
> --------------------------------------------------------------------------
>
> Key: THRIFT-3320
> URL: https://issues.apache.org/jira/browse/THRIFT-3320
> Project: Thrift
> Issue Type: Story
> Components: C++ - Library, Java - Library, Python - Library
> Affects Versions: 0.9, 0.9.1, 0.9.2
> Reporter: Xiaoshuang LU
> Attachments: THRIFT-3320.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
