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 2017/01/21 16:05:26 UTC

[jira] [Updated] (THRIFT-2504) As a developer, I want a server-side upgrade to MultiplexedProtocol to allow an older client to continue working in order to maintain backwards compatibility

     [ https://issues.apache.org/jira/browse/THRIFT-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James E. King, III updated THRIFT-2504:
---------------------------------------
    Summary: As a developer, I want a server-side upgrade to MultiplexedProtocol to allow an older client to continue working in order to maintain backwards compatibility  (was: TMultiplexedProcessor should allow registering default processor called if no service name is present)

> As a developer, I want a server-side upgrade to MultiplexedProtocol to allow an older client to continue working in order to maintain backwards compatibility
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 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)