[
https://issues.apache.org/jira/browse/THRIFT-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202402#comment-14202402
]
Hudson commented on THRIFT-2804:
--------------------------------
SUCCESS: Integrated in Thrift #1336 (See
[https://builds.apache.org/job/Thrift/1336/])
THRIFT-2804: java - TAsyncProcessor interface extracted from
TBaseAsyncProcessor (hcorg: rev fed887f9d9f563c123acafec9a0335e325e74a51)
* lib/java/src/org/apache/thrift/TBaseAsyncProcessor.java
* lib/java/src/org/apache/thrift/server/AbstractNonblockingServer.java
* lib/java/src/org/apache/thrift/TProcessorFactory.java
* lib/java/src/org/apache/thrift/TAsyncProcessor.java
> Pull an interface out of TBaseAsyncProcessor
> --------------------------------------------
>
> Key: THRIFT-2804
> URL: https://issues.apache.org/jira/browse/THRIFT-2804
> Project: Thrift
> Issue Type: Improvement
> Components: Java - Library
> Reporter: Michael Donaghy
> Assignee: Michael Donaghy
> Fix For: 0.9.3
>
>
> TNonblockingServer and friends are currently quite tightly coupled to
> TBaseAsyncProcessor, using an instanceof check to determine whether to use
> the async-processor or sync-processor code path. This makes it impossible to
> write a "custom" async processor, as any processor which is not a
> TBaseAsyncProcessor will use the sync code path (which behaves incorrectly
> with async processors).
> The idea is to separate out an interface, TAsyncProcessor. Custom async
> processors can then implement this interface and the server will take the
> async code path when used with such a processor.
> Code at https://github.com/apache/thrift/pull/253
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
