SessionWorkflow: use clientStrand only when necessary

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Service Arch 2022-10-17, Service Arch 2022-10-31, Service Arch 2022-11-14, Service Arch 2022-11-28, Service Arch 2022-12-12
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      ClientStrand is redundant when using dedicated thread model.
      So avoid it in the execution scheduling if it's not needed.
      Currently it's just used regardless and redundantly.

      The binding to ClientStrand is part of the scheduleNewLoop function currently.

            Assignee:
            Billy Donahue
            Reporter:
            Billy Donahue
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: