Github user gadLinux commented on the issue:
https://github.com/apache/thrift/pull/1361
@jeking3 I don't think binary and multi server can be compatible. In fact I
see it failing everytime and this is why I didn't set your protocol
recommendations.
Let me explain. When a mul
[
https://issues.apache.org/jira/browse/THRIFT-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196362#comment-16196362
]
ASF GitHub Bot commented on THRIFT-4329:
Github user gadLinux commented on the is
Github user gadLinux commented on the issue:
https://github.com/apache/thrift/pull/1361
What I'm thinking looking at Java implementation is that on c_glib we can
set a property in the processor to define what's the default handler to be get
in case of a not multi client. Let me see if
[
https://issues.apache.org/jira/browse/THRIFT-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196364#comment-16196364
]
ASF GitHub Bot commented on THRIFT-4329:
Github user gadLinux commented on the is
Github user gadLinux commented on the issue:
https://github.com/apache/thrift/pull/1361
Ok. Fixed a bug in the test client. And added the default protocol for the
multiplexed. That way the first registered protocol becomes default. This
allows you to use the multi without much hassle.
[
https://issues.apache.org/jira/browse/THRIFT-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196383#comment-16196383
]
ASF GitHub Bot commented on THRIFT-4329:
Github user gadLinux commented on the is
[
https://issues.apache.org/jira/browse/THRIFT-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196461#comment-16196461
]
Robert Lu commented on THRIFT-4271:
---
Firstly,
I don't think this is a Major bug.
And,
