Details

      Description

      Old way we used:
      ClusterExecutor has a thread pool, and run all the registered ClusterResponseCallback to do some post-processing with the ClusterResponse received.

      The new way we want to change to:
      Remove ClusterResponseCallback support, and make clients do the post-processing themselves.

      Reasons:
      1) API of ClusterExecutor would be more cleaner and simpler, the implementation of ClusterExecutor would be simplified without handling thread pool things.
      2) Clients would have more choice to do what the want, for example they can handle the response either in current thread or in another thread.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              shuyang.zhou Shuyang Zhou
              Reporter:
              tina.tian Tina Tian
              Recent user:
              Bryan Engler
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since last comment:
                6 years, 44 weeks, 2 days ago

                  Packages

                  Version Package
                  6.2.4 CE GA5
                  7.0.0 M5