并发ASP.NET最佳做法最坏的做法 [英] Concurrency ASP.NET best-practices worst-practices

问题描述

在这情况下，你需要注意并发性问题（并使用例如锁）在ASP.NET？

• 是否有关于这一主题围绕最佳实践


• 文档？


• 例子？


• 最坏的做法...'或者事情你见过，可能会导致一场灾难......？

我很好奇，例如单身（即使他们被认为是不好的做法 - 不要在此抛砖引玉），静态函数（你需要在这里观看了呢？），...

解决方案

由于ASP.NET是一个Web框架，主要是无国籍还有一些需要解决极少数并发的担忧。

这是我曾经处理的唯一事情是管理应用程序缓存，但是这很容易与包装了.NET的缓存机制缓存管理类型来完成的。

In which cases to you need to watch out for Concurrency problems (and use lock for instance) in ASP.NET?

• Are there 'best practices' around on this topic
• Documentation?
• Examples?
• 'worst practices...' or things you've seen that can cause a disaster...?

I'm curious about for instance singletons (even though they are considered bad practice - don't start a discussion on this), static functions (do you need to watch out here?), ...?

解决方案

Since ASP.NET is a web framework and is mainly stateless there are very few concurrency concerns that need to be addressed.

The only thing that I have ever had to deal with is managing application cache but this is easily done with a cache-management type that wraps the .NET caching mechanisms.

这篇关于并发ASP.NET最佳做法最坏的做法的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！