ASP.NET MVC 中 HttpRuntime.Cache 的使用是否发生了变化？

发布于 2024-07-07 01:24:27 字数 625 浏览 7 评论 0 原文

因此，在准备对控制器进行单元测试时，我正在查看我的标准缓存实用程序，并想，嘿，直接访问 HttpRuntime.Cache 在 MVC 中是否被认为是有害的？

我将缓存包装在一个代理类中，该类实现了类似缓存的接口（虽然简单得多），以便我可以在测试期间模拟它。但我想知道新框架中是否已经为我完成了这一点。然而我找不到任何东西。

以下是我如何做到这一点的想法：

public ActionResult DoStuffLol(guid id)
{
  var model = CacheUtil.GetOrCreateAndStore(
                  "DoStuffLolModel",
                  () =>
                  {
                    /* construct model here; time consuming stuff */
                    return model;
                  });
  return View("DoStuffLol", model);
}

那么，访问缓存的旧模式是否发生了变化？在 MVC 中是否有更好的缓存操作结果的模式？

原文

So, I was looking over my standard cache utility when preparing to unit test a controller and thought, hey, is accessing the HttpRuntime.Cache directly considered harmful in MVC?

I wrap the cache in a proxy class that implements a cache-like interface (tho much simpler) so that I can mock it during tests. But I'm wondering if that's already done for me in the new framework. I can't find anything, however.

Here's an idea of how I do it:

public ActionResult DoStuffLol(guid id)
{
  var model = CacheUtil.GetOrCreateAndStore(
                  "DoStuffLolModel",
                  () =>
                  {
                    /* construct model here; time consuming stuff */
                    return model;
                  });
  return View("DoStuffLol", model);
}

So, has the old patterns of accessing the cache changed? Are there any better patterns for caching action results in MVC?

分享到QQ

分享到微博