Uploaded image for project: 'Directory Client API'
  1. Directory Client API
  2. DIRAPI-310

We most certainly don't need a Queue in operation futures

Attach filesAttach ScreenshotWatch issueCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.0.0
    • 2.0.0.AM3
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            elecharny Emmanuel L├ęcharny
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment