[ https://issues.apache.org/jira/browse/THRIFT-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James E. King, III updated THRIFT-2504: --------------------------------------- Description: 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. Given that multiplex is just a decorated protocol where the service name is prepended to the call name, it should be possible to connect a standard binary protocol client to a multiplex protocol server that treats a non-multiplex call (one without the colon separator) as a backwards-compatible call so older clients can continue to connect to newer servers. (was: 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.) > 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. Given that multiplex is just a decorated protocol where the service > name is prepended to the call name, it should be possible to connect a > standard binary protocol client to a multiplex protocol server that treats a > non-multiplex call (one without the colon separator) as a > backwards-compatible call so older clients can continue to connect to newer > servers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)