You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2016/04/14 06:56:25 UTC
[jira] [Commented] (THRIFT-2504) TMultiplexedProcessor should allow
registering default processor called if no service name is present
[ https://issues.apache.org/jira/browse/THRIFT-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240598#comment-15240598 ]
James E. King, III commented on THRIFT-2504:
--------------------------------------------
Is this a change that needs to be made across all languages? What's the status of this issue, given it's about 2 years idle?
I think this is particularly important to the success of projects transitioning from a BinaryProtocol to a MultiplexedProtocol implementation and maintaining backwards compatibility.
> TMultiplexedProcessor should allow registering default processor called if no service name is present
> -----------------------------------------------------------------------------------------------------
>
> Key: THRIFT-2504
> URL: https://issues.apache.org/jira/browse/THRIFT-2504
> Project: Thrift
> Issue Type: Improvement
> Components: Java - Library
> Reporter: Aleksey Pesternikov
>
> Compatibility feature: TMultiplexedProcessor could be used with old clients when configured with old service as default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)