[jira] [Commented] (THRIFT-2504) TMultiplexedProcessor should allow registering default processor called if no service name is present

["James E. King, III (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/THRIFT-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874773#comment-15874773 ] 

James E. King, III commented on THRIFT-2504:
--------------------------------------------

After working on THRIFT-3706 I found that the Multiplexed Protocol wrapper is not compatible with older clients connecting.  It has its own protocol header that would not allow a binary client to connect and use the default processor.  As such, this change offers no benefit since one must use multiplexed on either end.  This should be reverted.

> 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
>            Assignee: James E. King, III
>             Fix For: 0.11.0
>
>
> The original intention of this story was to allow an older client to connect to a multiplexed server and continue to work by having the multiplexed processor handle any request that does not contain a service name and colon prefix.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)