[ https://issues.apache.org/jira/browse/THRIFT-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063073#comment-15063073 ]
ASF GitHub Bot commented on THRIFT-2427: ---------------------------------------- GitHub user nickdolgov opened a pull request: https://github.com/apache/thrift/pull/747 THRIFT-2427 Add support for Multiplexed Async Processors You can merge this pull request into a Git repository by running: $ git pull https://github.com/nickdolgov/thrift THRIFT-2427/20151217 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/thrift/pull/747.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #747 ---- commit eb2efe2d4447d0ef1aad91a199cf75bf4e310e7a Author: ndolgov <n...@beckon.com> Date: 2015-12-17T23:22:34Z THRIFT-2427 add support for TMultiplexedProcessor-style multiplexed async processor compatible with client requests made with TMultiplexedProtocol ---- > Add support for Multiplexed Async Processors > -------------------------------------------- > > Key: THRIFT-2427 > URL: https://issues.apache.org/jira/browse/THRIFT-2427 > Project: Thrift > Issue Type: Improvement > Components: Java - Library > Reporter: Lior Neudorfer > Attachments: TMultiplexedAsyncProcessor.java, > thrift_2427_add_support_for_multiplexed_async_processors.patch > > > THRIFT-1972 added support for Asynchronous processors to be used with Non > blocking servers. THRIFT-563 added support for multiplexed servers. > I would like to build a Non Blocking server which runs multiple, multiplexed > async processors. However, the current Java implementation does not allow a > multiplexed asynchronous server: > 1. TMultiplexedProcessor implements TProcessor, which causes > TNonBlockingServer to create a FrameBuffer, not a AsyncFrameBuffer for it. > 2. TMultiplexedProcessor calls the underlying processors with the > {code:xml}process(TProtocol in, TProtocol out){code} method variant, which > returns false in TBaseAsyncProcessor. It should, instead, be able to call the > {code:xml}process(final AsyncFrameBuffer fb){code} variant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)