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 2018/01/23 00:20:00 UTC

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

Emmanuel Lecharny created DIRAPI-310:
----------------------------------------

             Summary: 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
             Fix For: 2.0.0


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)