blocks|key|5252402|text|我一直在Windsor中使用缓存装饰器(而不是拦截器)，它们工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5252403|拦截器对此也很有帮助，参见this示例。|offset|length|5252404|entityMap|0|LINK|mutability|MUTABLE|url|http://ayende.com/Blog/archive/2007/03/11/AOP-With-Windsor-Adding-Caching-to-IRepositoryT-based-on-Ts.aspx^0|0|D|4|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I've been using caching decorators (not interceptors) with Windsor and they work great.

Interceptors are good for this as well, see <a href="http://ayende.com/Blog/archive/2007/03/11/AOP-With-Windsor-Adding-Caching-to-IRepositoryT-based-on-Ts.aspx" rel="nofollow noreferrer">this</a> for example.

blocks|key|3841925|text|嘿，我们已经使用了Castle+Windsor拦截器，基于这篇文章：http://www.davidhayden.com/blog/dave/archive/2007/03/14/CastleWindsorAOPPolicyInjectionApplicationBlock.aspx以及上面提到的那个。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3841926|我发现整个事情都很简单，这是一种非常优雅的AOP方法。然而……|3841927|不过，要小心性能。使用拦截创建了一个动态代理，这肯定会减慢速度。基于我们使用500节点计算场的基准测试，我们发现在Windsor中使用拦截的性能下降了大约30%25，这也超出了我们在拦截中所做的事情(本质上是记录方法调用和传入我们的方法的参数)。简单地删除拦截就可以大大加快整个应用程序的运行速度。|3841928|小心不要让你的昂贵的电话变得非常昂贵。:)如果我是你，我会考虑在不同的级别缓存，可能是通过实现一个IRepository类型模式，然后在适当的时候用各种缓存策略来支持它。|3841929|祝好运,|3841930|--|3841931|马特。|3841932|entityMap|0|LINK|mutability|MUTABLE|url|http://www.davidhayden.com/blog/dave/archive/2007/03/14/CastleWindsorAOPPolicyInjectionApplicationBlock.aspx^0|Y|30|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|15|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|16|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|Q|$R|$5|S|T|U|C|$V|W]]]]

Hey there, We've used Castle Windsor Interceptors, based on this article: <a href="http://www.davidhayden.com/blog/dave/archive/2007/03/14/CastleWindsorAOPPolicyInjectionApplicationBlock.aspx" rel="nofollow noreferrer">http://www.davidhayden.com/blog/dave/archive/2007/03/14/CastleWindsorAOPPolicyInjectionApplicationBlock.aspx</a> as well as the one mentioned above.

I found the whole thing pretty easy and it's a very elegant way to do AOP. However....

Careful with the performance though. Using interception creates a dynamic proxy that will definitely slow things down. Based on our benchmarks using a 500 Node computing farm we saw a performance decrease of about 30% by using interception in Windsor, this was outside what we were doing inside the interception as well (essentially logging method calls and params passed in to our methdods). and simply removing the interception sped the whole app up quite a bit. 

Careful you don't make your expensive calls really expensive. :) If I were you I would look to cache at a different level, probably by implementing an IRepository type pattern and then backing that with various caching strategies where appropriate. 

Good luck, 

-- 
Matt.

blocks|key|751934|text|您是如何实现数据访问的？如果你使用的是NHibernate，我建议在这里使用缓存。NHibernate为.NET内置缓存、memcached+(通过NMemcachD)和Velocity提供了缓存策略。我已经广泛地将memcached用于企业级应用程序，并且没有遇到任何问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|751935|基于拦截器的缓存机制是一个有趣的想法，我以前从未想过这个想法。这将非常容易透明地应用。我认为我喜欢使用Castle的AOP特性是因为它是基于代理的，你不必用属性污染你的代码。|751936|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

How are you implementing your data access? If your using NHibernate, I would suggest caching here. NHibernate comes with cache strategies for the .NET built-in cache, memcached (via NMemcachD) and Velocity. I've used memcached extensivly for enterprise level applications and have not had a problem with it.

An intercepter based caching mechanism is an interesting idea, one I haven't thought of before. It would be very easy to transparently apply. The one think I love about using the AOP features of Castle is because it's proxy based, you don't have to pollute your code with attributes.

blocks|key|3841726|text|我会看看Microsoft+Velocity。如果您计划创建一个Enterprise应用程序，这可能是一个很好的解决方案|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3841727|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/data/cc655792.aspx^0|4|I|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I'd look at the <a href="http://msdn.microsoft.com/en-us/data/cc655792.aspx" rel="nofollow noreferrer">Microsoft Velocity</a>. If you plan on creating an Enterprise application, this might be a good solution

blocks|key|3842013|text|我在一个名为cachew.castlewindsor的开源项目上创建了一个缓存拦截器。它是一种通用的缓存解决方案。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3842014|下面是一个简单的用法示例：|3842015|var+container+=+new+WindsorContainer();+container.Register(Component.For<CacheInterceptor>()+++.Instance(new+CacheInterceptor(new+Cache(TimeoutStyle.RenewTimoutOnQuery,+TimeSpan.FromSeconds(3)))));+container.Register(Component.For<IServer>().ImplementedBy<Server>().Interceptors<CacheInterceptor>());|CODE|3842016|默认行为是缓存所有以Get和return数据开头的方法，但您也可以更改缓存的前缀。|3842017|该项目可在nuget上获得：http://www.nuget.org/packages/Cachew.CastleWindsor/|3842018|源代码可以在这里找到：https://github.com/kobbikobb/Cachew|3842019|entityMap|0|LINK|mutability|MUTABLE|url|http://www.nuget.org/packages/Cachew.CastleWindsor/|1|https://github.com/kobbikobb/Cachew^0|6|K|0|0|0|8C|0|0|E|1F|0|0|B|Z|1|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|13|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|14|8|@$9|15|A|16|B|J]]|D|@]|E|$]]|$1|K|3|L|5|6|7|17|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|O|3|P|5|6|7|1C|8|@]|D|@$9|1D|A|1E|1|1F]]|E|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]|Y|$5|T|U|V|E|$W|Z]]]]

I created on open source project named cachew.castlewindsor with a caching interceptor.
It is a general purpose solution for caching.

Here is a simple example of usage:

<code>var container = new WindsorContainer();
container.Register(Component.For&lt;CacheInterceptor&gt;()
 .Instance(new CacheInterceptor(new Cache(TimeoutStyle.RenewTimoutOnQuery, TimeSpan.FromSeconds(3)))));
container.Register(Component.For&lt;IServer&gt;().ImplementedBy&lt;Server&gt;().Interceptors&lt;CacheInterceptor&gt;());</code>

The default behaviour is to cache all methods that starts with Get and return data, but you can also change what prefixes to cache.

The project is available on nuget: 
<a href="http://www.nuget.org/packages/Cachew.CastleWindsor/" rel="nofollow">http://www.nuget.org/packages/Cachew.CastleWindsor/</a>

And the source code is available here:
<a href="https://github.com/kobbikobb/Cachew" rel="nofollow">https://github.com/kobbikobb/Cachew</a>

blocks|key|751873|text|Windsor很棒，但是当你有几种内置的缓存数据的方法时，为什么还要使用它来缓存数据呢？Windsor在其他领域有自己的基础，不一定是缓存。从缓存对象到会话再到cookie。缓存的方式有很多。更重要的是，在大型应用程序中，最终需要分布式缓存。微软正在为此开发一款产品，市场上有几家优秀的供应商。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|751874|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Windsor is great, but why use that for caching when you have several built in ways to cache data. Windsor has its foundation in other areas not necessarily caching. From the cache object to session to cookies. There are many ways to cache. More importantly in large applications you end up needing distributed caching. MS is working on a product for that and there are a couple good vendors out there that have products on the market.

I'm considering using Castle Windsor's Interceptors to cache data for helping scale an asp.net site.

Does anyone have any thoughts/experience with doing this?

Minor clarification:
My intention was to use Windsor to intercept 'expensive' calls and delegate to MemCacheD or Velocity (or another distributed cache) for the caching itself.

Windsor Interceptors AOP & Caching

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在考虑使用Castle Windsor的拦截器来缓存数据，以帮助扩展asp.net站点。有没有人有这样做的想法/经验？次要说明:我的意图是使用Windsor截取“昂贵的”调用，并将其委托给MemCacheD或Velocity (或另一个分布式缓存)进行缓存本身。

问Windsor拦截器AOP和缓存
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Windsor拦截器AOP和缓存EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Windsor拦截器AOP和缓存
EN