thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (THRIFT-2427) Add support for Multiplexed Async Processors
Date Wed, 24 Jan 2018 00:55:01 GMT

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

ASF GitHub Bot commented on THRIFT-2427:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/thrift/pull/747


> 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
>            Priority: Major
>         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
(v7.6.3#76005)

Mime
View raw message