It looks like there's a deeper issue here, and I don't quite understand the use case. Are two clients being used on the same transport? As far as I know, this isn't supported by any of the implementations today. Recommend opening multiple connections to the server - one for each client, even if they are in the same process. While the change proposed perhaps moves in the direction stated, I'm not convinced proper locking would be done to avoid interleaving message contents and corrupting the stream.
This issue has no Jira ticket and has been idle for a long time. I'm going to close it. It can be reopened in the future by opening a Jira ticket. [ Full content available at: https://github.com/apache/thrift/pull/1093 ] This message was relayed via gitbox.apache.org for [email protected]
