何时使用“动态代理类”或“标准代理”模式？(When to use “Dynamic Proxy class” or “standard proxy” pattern?)

 为什么要使用“动态代理类”而不是“标准代理”模式？ 
 
 两者的缺点或优点是什么？ 
 
 看起来它们都有相同的最终结果，除了它们的实现方式不同。 
 
 动态代理类https://docs.oracle.com/javase/8/docs/technotes/guides/reflection/proxy.html 
 
 
 
 动态代理类是实现在运行时指定的接口列表的类，这样通过类的实例上的一个接口的方法调用将被编码并通过统一接口分派给另一个对象。 因此，动态代理类可用于为接口列表创建类型安全的代理对象，而无需预生成代理类，例如使用编译时工具。 动态代理类实例上的方法调用被分派到实例的调用处理程序中的单个方法，并使用标识被调用方法的java.lang.reflect.Method对象和包含该方法的Object类型数组进行编码。参数。 
 
 
 标准代理模式https://en.wikipedia.org/wiki/Proxy_pattern 
 
 
 
 代理以其最一般的形式，是一个充当其他东西的接口的类。 代理可以与任何东西连接：网络连接，内存中的大对象，文件或其他昂贵或无法复制的资源。 简而言之，代理是一个包装器或代理对象，客户端正在调用它来访问幕后的真实服务对象。 在代理中，可以提供额外的功能，例如当真实对象上的操作是资源密集时的高速缓存，或者在调用真实对象上的操作之前检查先决条件。 对于客户端，代理对象的使用类似于使用真实对象，因为两者都实现相同的接口。 
 

Why should one use a "Dynamic Proxy class" instead of the "standard proxy" pattern? 
 
What are the disadvantages or advantages of both?
 
It seems like they both have the same end result, except that they are implemented differently.
 
Dynamic proxy class https://docs.oracle.com/javase/8/docs/technotes/guides/reflection/proxy.html
 
 
 
A dynamic proxy class is a class that implements a list of interfaces specified at runtime such that a method invocation through one of the interfaces on an instance of the class will be encoded and dispatched to another object through a uniform interface. Thus, a dynamic proxy class can be used to create a type-safe proxy object for a list of interfaces without requiring pre-generation of the proxy class, such as with compile-time tools. Method invocations on an instance of a dynamic proxy class are dispatched to a single method in the instance's invocation handler, and they are encoded with a java.lang.reflect.Method object identifying the method that was invoked and an array of type Object containing the arguments.
 
 
Standard proxy pattern https://en.wikipedia.org/wiki/Proxy_pattern
 
 
 
A proxy, in its most general form, is a class functioning as an interface to something else. The proxy could interface to anything: a network connection, a large object in memory, a file, or some other resource that is expensive or impossible to duplicate. In short, a proxy is a wrapper or agent object that is being called by the client to access the real serving object behind the scenes. In the proxy extra functionality can be provided, for example caching when operations on the real object are resource intensive, or checking preconditions before operations on the real object are invoked. For the client, usage of a proxy object is similar to using the real object, because both implement the same interface.
 

原文：https://stackoverflow.com/questions/35279850