WS-SecureConversation encrypting all request/response message bodies (securconv)
加密所有请求/响应消息体的 WS-SecureConversation（securconv）
To be of any benefit, WS-SecureConversation requires an ongoing sequence of messages over a relatively short span of time.
为了能获取收益，WS - SecureConversation需要正在持续的消息序列处于相对较短时间内。
Along the way to the performance results, you'll also see the details of configuring WS-SecureConversation on the three stacks.
并且在获得此性能成果的过程中，您还将看到在这三个堆栈上配置WS - SecureConversation的细节。
As you can see in Figure 2, WS-SecureConversation encryption does provide a significant performance improvement over WS-Security.
如图2所示，WS - SecureConversation加密确实相对WS - Security提供显著的性能改善。
The Rampart distribution includes a separate module called rahas, which enables issuing security tokens required by WS-SecureConversation.
Rampart发行版包括一个单独的rahas模块，它支持发起WS - SecureConversation所需的安全令牌。
In these cases, WS-Security (or its offspring, WS-SecureConversation) is required, and the performance cost is simply a necessary expense.
在这些情况中，就必须使用WS - Security(或者它的后代WS - SecureConversation)，而且性能成本也成为必要的开销。
One advantage of WS-SecureConversation is supposed to be a performance gain from using symmetric encryption rather than asymmetric encryption.
WS - SecureConversation的一个优势是使用对称加密比使用非对称加密更能取得性能收益。
This approach offers good performance for message exchanges - nearly as good as WS-SecureConversation - when the messages are relatively large.
当消息相对较大时，这个方法在实现消息交换时有很好的性能—几乎与WS - SecureConversation一样好。
WS-SecureConversation is a standard that builds on the WS-Security and WS-Trust standards to support secure exchanges involving multiple messages.
WS - SecureConversation是在WS - Security和WS -Trust标准之上构建的一种标准，用于支持涉及多个消息的安全交换。
WS-SecureConversation in theory can be used with multiparty message exchanges, but the most common usage is for a client communicating with a single server.
WS-SecureConversation在理论上可以用于多方的消息交换，但它最为常见的用法是用在一个客户机与一个服务器之间的通信。
These results show that WS-Security symmetric encryption with client-generated keys is nearly as fast as WS-SecureConversation, especially for larger messages.
这些结果表明使用客户端生成的密钥进行WS - Security对称加密几乎和WS - SecureConversation一样快，特别是对于较大的消息。
Because this means Axis2 USES a canned configuration for its WS-SecureConversation support, it's only compatible with other stacks using that same configuration.
这意味着Axis2为其WS - SecureConversation支持使用千篇一律的配置，它只与其他使用相同配置的栈可兼容。
The performance advantage is much less pronounced in the case of larger messages, but WS-SecureConversation is still a respectable 18 percent faster in that case.
而对于较大的消息来说，性能优势则逊色许多，但WS - SecureConversation仍然提供了18%的速度提升。
The problems I found with Axis2 include WS-SecureConversation policy handling, wherein the bootstrap policy definition appears to be completely ignored in operation.
我在Axis2 中发现的问题包括WS-SecureConversation策略处理，其中引导程序策略定义在运行过程中似乎被完全忽略了。
WS-SecureConversation overcomes the restriction of WS - Security to a round of a single secured message between a monitored Web service and a monitoring Web service.
WS - SecureConversation克服了WS -Security在被监视Web服务和监视Web服务之间仅传递单个安全消息的限制。
Limited interoperability testing (using one stack for the client and another for the server, only tried for the WS-SecureConversation tests) demonstrated even more issues.
有限的互操作性测试(每个客户端使用一个栈，服务器使用另一个，只尝试WS - SecureConversation测试)会显示更多的问题。
In this article, you'll see how you can go a step further and break free of the need for client certificates in both plain WS-Security and WS-SecureConversation exchanges.
在本文中，您将会了解您可以如何更一步地打破在普通的WS - Security和WS - SecureConversation交换方面都需要客户端证书的现状。
This is especially true in the case of smaller messages, for which the WS-SecureConversation configuration was almost twice as fast as WS-Security encryption using certificates.
这对于较小的消息尤为明显，其WS - SecureConversation配置的运行速度几乎是使用证书的WS - Security加密的两倍。
The gateway model can include applying authentication and authorization to incoming messages using the Apache Rampart framework to support WS-Security and WS-SecureConversation.
网关模型可以包括使用ApacheRampart框架应用身份验证机制、以及对进入的消息进行授权，以支持WS - Security和WS - SecureConversation。
WS-SecureConversation: Describes how to manage and authenticate message exchanges between parties, including security context exchange and establishing and deriving session keys.
WS - SecureConversation：描述如何管理和认证各方之间的消息交换，包括安全上下文交换以及建立和继承会话密钥。
Though not shown in this article, this use of secret keys is essentially the same as the signing example for WS-SecureConversation discussed in "WS-SecureConversation performance."
虽然本文没有介绍，但是保密密钥的使用方法本质上与“WS - SecureConversation性能”中讨论的WS - SecureConversation签名例子是一样的。
The signing-only test results are much faster using WS-SecureConversation symmetric encryption for the case of small responses, but this advantage is lost when large responses are returned.
在小响应中使用WS-SecureConversation对称加密的仅签名测试结果要快得多，但当返回大响应时，其优势丧失。
This makes it difficult to provide any direct performance comparison, but you can get an idea of the difference by comparing these charts with those from "WS-SecureConversation performance."
这使得我们很难作直接的性能比较，但是您可以通过将这些图表与“WS - SecureConversation性能”中的图表进行比较来了解它们之间的区别。
The earlier article showed that WS-SecureConversation symmetric encryption provides considerably better performance than WS-Security asymmetric encryption, especially for encrypting messages.
前一篇文章显示WS - SecureConversation对称加密显然比WS - Security不对称加密具有更好的性能，特别是在加密消息时。
When you use WS-SecureConversation: two separate security configurations are present in the policy for the service, one for the message exchange with the STS and the other for the target service.
当使用WS-SecureConversation 时：两个单独的安全配置出现在服务策略中，一个用STS用于消息交换，另一个用于目标服务。
A big difference is that when WS-SecureConversation is used, the policy must cover two separate exchanges - that between the client and the STS, and that between the client and the actual service.
一个大的区别在于当使用WS - SecureConversation时，此策略必须涵盖两种不同的交换—即客户机与STS之间的交换以及客户机与实际的服务之间的交换。
In the next article, you'll learn about the WS-Trust and WS-SecureConversation add-on technologies, which can reduce the WS-Security overhead when clients make extensive use of a particular service.
在下一篇文章中，您将了解WS - Trust和WS - SecureConversation增件技术，该技术可以在客户机广泛使用特定服务时降低WS - Security开销。
In the next article, you'll learn about the WS-Trust and WS-SecureConversation add-on technologies, which can reduce the WS-Security overhead when clients make extensive use of a particular service.
在下一篇文章中，您将了解WS - Trust和WS - SecureConversation增件技术，该技术可以在客户机广泛使用特定服务时降低WS - Security开销。
应用推荐