Skip to content

InvocationContext is not thread safe? #20

Description

@htzhang2

Two threads both write to InvocationContext in BeforeInvoke method:

  1. Thread1:
    invocationCopntext.SetTemporaryData("temp", "value1");

  2. Thread2:
    invocationCopntext.SetTemporaryData("temp", "value2");

This seems corrupt invocationContext.

Is there a thread safe solution?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions