The only important DI piece missing is dynamic proxies and interception.
DI现在缺少的重要功能只有动态代理和拦截器了。
One solution, therefore, is to use dynamic proxies in some areas and not in others.
所以，有一种解决方案，就是在有些地方用动态代理，在其他地方则不用。
Dynamic proxies are classes that implement a set of interfaces specified at runtime.
动态代理是这样一种类，它可以实现在运行时指定的一组接口。
In this article, you saw the benefits of using dynamic proxies with an invocation handler.
在这篇文章里，您看到了用调用处理使用动态代理的好处。
Unlike a tightly coupled approach, using dynamic proxies leaves you with validation code that is reusable and configurable.
与紧密耦合方法不同，使用动态代理给您带来了可以重用、可以配置的验证代码。
Dynamic proxies provide a simple mechanism to invoke a Web service without requiring much knowledge about the underlying XML.
动态代理提供一种简单机制来调用Web服务，不需要您深入了解底层XML。
Dynamic proxies provide access to service endpoint interfaces (SEIs) at run time without requiring static generation of a stub class.
动态代理支持在运行时访问服务端点接口(SEI)，不需要静态生成stub类。
As with any technology, you should carefully evaluate the alternatives and use dynamic proxies only when they are the best solution for your application.
使用任何一种技术，您都应当仔细评估替代品，只有当动态代理是应用程序的最佳解决方案时才使用它。
Because validation is often a pre-method invocation operation, dynamic proxies provide us with a solution to the problems outlined in the previous examples.
因为验证通常是方法前调用操作，所以动态代理为我们提供了针对前面示例所指出的问题的解决方案。
With all that was said so far, you can easily think in terms of using any kind of dynamic invocation techniques (such as dynamic proxies for late binding) like, unfortunately, many developers do.
根据到目前为止的讲述，您容易想到使用任何种类的动态调用技术（如后期绑定的动态代理），不幸的是，许多开发者都是这样做的。
These are the proxies generated for a particular.net language and then compiled to dynamic link libraries using the appropriate.net compiler for the language.
这些是为特殊的. NET语言所生成的，然后使用针对这种语言的恰当的. NET编译器被编译成动态链接库的代理。
The JDK dynamic proxy, which has been available since JDK 1.3, is often used to create proxies dynamically.
JDK自从1.3版本开始，就引入了动态代理，并且经常被用来动态地创建代理。
The servers themselves run nginx, which handles static requests and proxies any dynamic requests to mongrel instances.
服务器本身运行nginx，来处理静态请求并将任何动态请求委托给混合实例。
(These proxies can be static or dynamic).
(这些代理可以是静态的或者动态的)。
I'm not going to define properties on my domain objects - I defer that to Groovy's dynamic nature (which allows me, in essence, to make my domain objects proxies to Google's Entity objects).
我不打算定义我的域对象上的属性—我将其推迟到Groovy的动态特性(实际上，这个特性允许创建针对Google的Entity对象的域对象代理)。
I'm not going to define properties on my domain objects - I defer that to Groovy's dynamic nature (which allows me, in essence, to make my domain objects proxies to Google's Entity objects).
我不打算定义我的域对象上的属性—我将其推迟到Groovy的动态特性(实际上，这个特性允许创建针对Google的Entity对象的域对象代理)。
应用推荐