.NET 列出需要的线程安全实施建议

发布于 2024-12-05 06:30:07 字数 893 浏览 1 评论 0原文

.Net List 类不是线程安全的。我希望实现所需的最小锁定，但仍然满足要求，例如对于读取，允许幻象记录，对于写入，它们必须是线程安全的，这样就不会丢失任何更新。

所以我所做的

public static List<string> list = new List<string>();

In Methods that have **List.Add**/**List.Remove** , I always lock to assure thread safety

            lock (lockHelper)
            {
                    list.Add(obj);
                    or list.Remove(obj);
            }

In Methods that requires **List Reading** I don't care about phantom record so I go ahead to read without any locking. In this case. Return a bool by checking whether a string had been added.

          if (list.Count() != 0) {
              return list.Contains("some string")
          }

就是锁定写访问，并允许读访问在没有任何锁定的情况下进行。我的线程安全想法有效吗？

据我所知，列表大小有所扩展。会好吗？我的猜测是，当列表扩展时，它可能会使用临时变量。列表。这是可以的，因为临时列表大小总是有一个边界，并且 .Net 类实现得很好，即。当读取被更新时，不应该出现任何indexOutOfBound或循环引用问题。

原文

.Net List class isn't thread safe. I hope to achieve the minimal lock needed and yet still fulfilling the requirement such that as for reading, phantom record is allowed, and for writing, they must be thread-safe so there won't be any lost updates.

So I have something like

public static List<string> list = new List<string>();

In Methods that have **List.Add**/**List.Remove** , I always lock to assure thread safety

            lock (lockHelper)
            {
                    list.Add(obj);
                    or list.Remove(obj);
            }

In Methods that requires **List Reading** I don't care about phantom record so I go ahead to read without any locking. In this case. Return a bool by checking whether a string had been added.

          if (list.Count() != 0) {
              return list.Contains("some string")
          }

All I did was locking write accesses, and allow read accesses to go through without any locking. Is my thread safety idea valid?

I understand there is List size expansion. Will it be ok? My guess is that when a List is expanding, it may uses a temp. list. This is ok becasue the temp list size will always have a boundary, and .Net class is well implemented, ie. there shouldn't be any indexOutOfBound or circular reference problems when reading was caught in updates.

分享到QQ

分享到微博