Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-46619

Move Baton to Client

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • v4.4
    • Service Arch 2020-03-09, Service Arch 2020-03-23, Service Arch 2020-04-06, Service arch 2020-04-20
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Each OperationContext has its own Baton attached here. We can instead attach the Baton to the Client and have each OperationContext have a SubBatonHolder instead. This may affect performance in unforeseen ways, so this will require general perf verification. Also note that the AsyncRequestsSender will now be making a SubBaton of a SubBaton.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: