[
https://issues.apache.org/jira/browse/THRIFT-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059795#comment-15059795
]
Jan Sileny commented on THRIFT-2427:
------------------------------------
Hello,
your suggestions are right, code is better isolated this way and it seems
prettier, you are much more familiar with thrift than me. Well, I was not able
to work more on this since my initial proposal, so it went on its own. What
more I am still in a complete hurry with some other projects, so if you could,
please do make some pull request. I will try and test it on my projects as soon
as possible.
Have a nice end of year.
J.
> 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)
