这个问题的可行解决方案？

发布于 2024-10-25 20:11:50 字数 541 浏览 7 评论 0原文

我通过多层第三方代码从我的一段代码进行调用，并且通过调用我编写的一些代码，该调用在某个时刻返回到我的代码中。

换句话说，代码调用链如下所示：

My code #1 --> 3rd party code --> My code #2

不幸的是，我传递给第 3 方代码的任何内容都没有传递给第二段代码，因此我没有任何东西可以将第一段和第二段代码连接在一起，除了以下事实：代码在同一个线程上运行。

所以我想知道在类的静态字段上简单地使用 [ThreadStatic] 是否是一个可行的解决方案？

由于代码也在 Web 应用程序中运行，因此我不能仅使用静态字段来实现此目的，因为每个用户/会话需要访问的值（对象）都不同。

IE。我会做这样的事情：

internal static class DataHolder
{
    [ThreadStatic]
    internal static ClassName FieldName;
}

还有其他解决方案吗？

原文

I am calling from one piece of my code through several layers of 3rd party code, and the call surfaces back into my code at some point by calling some code I've written.

In other words, the code call chain looks like this:

My code #1 --> 3rd party code --> My code #2

Unfortunately, nothing I pass to the 3rd party code is given to that second piece of code so I have nothing to tie the first piece and the second piece together, except for the fact that the code runs on the same thread.

So I was wondering if simply using [ThreadStatic] on a static field on a class would be a viable solution to this?

Since the code also runs in a web application, I cannot just use a static field for this, since the value I need access to (an object) is different for each user/session.

ie. I would do something like this:

internal static class DataHolder
{
    [ThreadStatic]
    internal static ClassName FieldName;
}

Are there other solutions to this?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

ぶ宁プ宁ぶ 2024-11-01 20:11:50

与建议这没问题的其他答案相反，在 ASP.NET 应用程序中使用 ThreadStatic 或 ThreadLocal时，您应该非常小心。

ASP.NET 利用线程敏捷性，这意味着同一请求可能由多个线程处理。为了安全起见，您需要打破封装并将项目存储在当前的 HttpContext 中，而不是使用 ThreadStatic 或 ThreadLocal：

internal static class DataHolder
{
    internal static ClassName PropertyName
    {
        get { return (ClassName)System.Web.HttpContext.Current.Items["foo"]; }
        set { System.Web.HttpContext.Current.Items["foo"] = value; }
    }
}

不幸的是，这种线程敏捷性“功能”的记录非常少。我有理由确信线程切换只能在生命周期中的某些点发生，而不是任意发生，因此根据代码在生命周期中的具体使用方式和位置，您可能可以安全地使用 ThreadStatic 或 ThreadLocal。

我会尝试挖掘一些链接......

In contrast to the other answers suggesting that this is ok, you should be very careful about using ThreadStatic or ThreadLocal<T> in an ASP.NET application.

ASP.NET utilises thread-agility, meaning that the same request can potentially be handled by several threads. To be safe you'd need to break encapsulation and store your items in the current HttpContext, rather than using ThreadStatic or ThreadLocal<T>:

internal static class DataHolder
{
    internal static ClassName PropertyName
    {
        get { return (ClassName)System.Web.HttpContext.Current.Items["foo"]; }
        set { System.Web.HttpContext.Current.Items["foo"] = value; }
    }
}

Unfortunately this thread-agility "feature" is very poorly documented. I'm reasonably sure that the thread switch can only happen at certain points in the lifecycle, not arbitrarily, so depending on exactly how and where in the lifecycle the code is used you might be safe with ThreadStatic or ThreadLocal<T>.

I'll try to dig out some links...

回复收藏 0 原文