OperationContext should have a constant id for whole lifetime

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 3.1.4
    • Affects Version/s: None
    • Component/s: Internal Code, Usability
    • None
    • Minor Change
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently it uses CurOp's id, but CurOps can be nested and the nested CurOps each have their own id. Instead, the OperationContext should get an ID at construction time and use the same ID until it is over.

              Assignee:
              Andy Schwerin
              Reporter:
              Mathias Stearn
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: