The performance overhead of a proxy-based approach can be an issue in a small minority of cases.
基于代理的方法的性能负载在少数案例中成为问题。
Ramnivas discussed the advantages and limitations of AspectJ weaving and proxy-based Spring AOP approach.
Ramnivas讨论了AspectJ织入和基于代理的SpringAOP方法的优势与不足。
Spring 2.0 provides an additional option for @AspectJ aspects: Spring can use its proxy-based AOP runtime to apply such aspects to Spring beans.
Spring 2.0为@AspectJ切面提供一种额外的选择：Spring可以使用它的基于代理的AOP运行时来将这样的切面应用到Spring beans。
But one of the best features of AOP is that it comes in several different flavors and implementations (i.e., proxy-based, byte-code weaving etc...).
但是AOP最好的特性之一就是它可以有多种不同的风格和实现(例如，基于代理的，字节码编织等等……)。
Spring AOP unfortunately can't help us here simply because it is proxy-based and since our intercepting filters are already a part of a proxy infrastructure we simply cannot proxy the proxy.
不幸的是SpringAOP不能帮上忙，因为它是基于代理的，因此我们的拦截过滤器已经是代理基础架构的一部分了，我们不能代理这个代理（proxythe proxy）。
This class allows creating a service proxy based on the interface and endpoint address and binding, which are built using information provided by the registry service.
这个类可以通过服务注册中心提供的接口，端点地址和绑定信息创建一个服务代理。
One submits the method of ID authentication based on proxy ARP.
有人提出了基于代理 ARP的ID认证方法。
The proxy filters calls based on data from the plugin.xml file (as returned by IConfigurationElement).
代理根据 plugin.xml文件中的数据（由 IConfigurationElement返回）过滤调用。
A secure proxy server can route requests based on either static or dynamic information.
安全代理服务器可以根据静态或动态信息路由请求。
When configured in high security mode, the secure proxy server will route application requests based on static route data.
当配置为高级安全模式时，安全代理服务器将根据静态路由信息路由应用程序请求。
The main idea behind AOP is that you create new typed object, based on a dynamic proxy mechanism, that implements a set of interfaces at runtime.
AOP背后的主要思想是基于动态代理机制创建新的对象类型，该对象会在运行时实现一些接口。
This option allows a reverse proxy to route traffic to the appropriate destination, based on information contained in the target URL.
该选项允许反向代理根据目标URL中包含的信息将传输路由到适当的目的地。
As described in this Information Center article, the SIP side of the proxy has the ability to route to a cluster based on a variety of mechanisms, including the message type explained in my example.
如这篇信息中心文章中所述，代理的sip侧有能力基于各种机制路由到集群，包括在我的示例中介绍的消息类型。
The proxy cache in front of your Web application reassembles the final document based on the parts, and is responsible for caching some components and making the request for others.
Web应用程序前面的代理缓存根据各个部分重新组装最终的文档，负责缓存一些组件并为其他组件发出请求。
When there is an error due to policy violations based on the current white list in effect, the proxy sends a custom JSON error object back to the browser. See listing 1.
根据当前生效的白名单，因策略违规而导致错误时，代理会向浏览器发送一个自定义的JSON错误对象，如清单1所示。
Instead, you are simply using a regular proxy server (defined in the same cell as the application servers) and routing based on dynamic information.
相反，您仅仅使用一个常规代理服务器(在与应用服务器相同的cell中定义)并根据动态信息执行路由。
The proxy is servlet based, and can be embedded directly in an EAR file or run on your server as a WAR file.
这个代理基于的是servlet，可直接嵌入到EAR文件或作为WAR文件运行于服务器。
To overcome the same-origin policy restriction, WebSphere Portal offers a solution that is based on a server-side HTTP proxy, the Ajax proxy layer.
为了克服相同来源的限制，WebSpherePortal提供了一个基于服务器端的HTTP代理方案，也就是Ajax 代理层。
A servlet-based Ajax proxy that can be embedded in your application.
一个基于servlet的Ajax代理，可被嵌入到您的应用程序。
This request is made back through the proxy servers for the affinity-based routing.
此请求通过代理服务器返回，以进行基于关联的路由。
ModSecurity works equally well when deployed as part of an Apache-based reverse proxy server, and many of our customers choose to do so.
在基于apache的反向代理模式上ModSecurity同样能工作的很好，我们很多客户选择这样做。
Using the REST-based HTTP GET method, the XML proxy will look to see if the request is cached in the simple data grid.
通过使用基于REST的HTTPGET方法，XML代理将查看请求是否缓存在简单数据网格中。
Generate EJB-based deployed code for the service, including code that ACTS as a proxy for the legacy program.
生成用于服务的基于EJB的部署代码，包括充当旧程序代理的代码。
One way of adding the required custom logic to your runtime is to generate a JAX-RPC based SOAP proxy.
向运行时添加所需的自定义逻辑的方法之一是生成基于JAX - RPC的SOAP代理。
Additionally, the proxy can filter on HTTP headers, cookies, and mime-types to provide a level of control over the sites that a browser-based client can access.
另外，该代理可以对HTTP标头、cookie和MIME类型进行筛选，以便对基于浏览器的客户端访问的网站提供一定级别的控制。
The registry is fully accessible via its Web services interface, and it exposes a set of WSDL and XML Schema definitions that you can use to generate a JAX-RPC-based proxy.
注册中心完全可以通过其Web服务接口进行访问，并且它公开了一组WSDL和XML模式定义，您可以将其用于生成基于JAX-RPC 的代理。
The feature pack provides a servlet-based forward proxy that can be used in the aggregation of content from different sites.
该FeaturePack提供基于servlet的转发代理，可以使用该转发代理聚合不同网站的内容。
The Web service proxy is a feature rich WSDL-based proxy for Web service providers.
WebServiceProxy是一个功能丰富的、基于WSDL的代理，面向Web服务提供者。
A Web service Proxy can contain one or more WSDL-based services, as shown in Figure 2.
一个WebServiceProxy可以包含一个或多个基于WSDL的服务，如图2所示。
The Web service Proxy is a configuration construct that encapsulates and ultimately defines how a WSDL-based service transaction is processed.
WebServiceProxy是一个配置构造，用于封装并最终定义如何处理基于WSDL的服务事务。
应用推荐