[jira] [Commented] (THRIFT-2427) Add support for Multiplexed Async Processors

["Nikita Dolgov (JIRA)" <ji...@apache.org>]

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

Nikita Dolgov commented on THRIFT-2427:
---------------------------------------

In case it might inspire someone to do a code review, I'd like to remind about a pull request open for this issue. It supersedes the attached patch even though it essentially re-packages the same code.

> 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)