You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2019/05/12 05:56:00 UTC

[jira] [Updated] (DIRAPI-310) We most certainly don't need a Queue in operation futures

     [ https://issues.apache.org/jira/browse/DIRAPI-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRAPI-310:
-------------------------------------
    Fix Version/s:     (was: 2.0.0)
                   2.0.0.AM3

> We most certainly don't need a Queue in operation futures
> ---------------------------------------------------------
>
>                 Key: DIRAPI-310
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-310
>             Project: Directory Client API
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>            Reporter: Emmanuel Lecharny
>            Priority: Major
>             Fix For: 2.0.0.AM3
>
>
> Currently, each operation future holds a {{BlockingQueue}} that will contain the response. This queue is stored in the inherited {{ResponseFuture}} class.
> This is a waste for most of the operation except {{SearchFuture}} and {{ExtendedFuture}} that might get more than one response. We could move the queue to the classes that nees it, and use a simple field for the other classes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)