Once this type of support exists, support for MakeConnection becomes trivial.
只要存在这种类型的支持，对MakeConnection的支持就会微不足道了。
See the MakeConnection example in the appendix of the WS-RM specification for more details.
有关更多细节，请参见WS -RM规范的附录中的MakeConnection示例。
The receipt of a message using MakeConnection should be viewed as nothing more than another transport.
使用MakeConnection接收消息的过程应该仅被视为另一个传输。
When a MakeConnection is received by an endpoint, it shouldn't go out of its way to construct a message.
当端点接收到MakeConnection时，不应着手构造消息。
The use of MakeConnection, as described above, allows any message targeted to the specified URI to be transferred.
如上所述，通过使用MakeConnection，可允许传输任何以指定URI为目标的消息。
However, since MakeConnection is extensible, implementations are free to define this type of identification element if they have a need for it.
不过，由于MakeConnection是可扩展的，实现可以在需要的情况下自由地定义这种类型的标识元素。
In order to support MakeConnection, as with many new features of any Web services specification, existing SOAP implementations will be impacted.
和任何Web服务规范的新功能一样，为了支持MakeConnection，将会对现有SOAP实现造成影响。
If the receiver of a MakeConnection does not have messages ready to be sent to the initiator of that connection, then an empty response should be sent back.
如果MakeConnection接收者没有要发送到该连接的发起者的消息，则应该发回一个空响应。
So, because MakeConnection allows any message targeted to that URI to be sent, it doesn't require additional constraints (like the use of sequences) on the sending endpoint.
因此，由于MakeConnection允许发送任何以该URI为目标的消息，因此并不要求对发送端点施加其他约束(例如，序列的使用)。
The MakeConnection element allows for other identifying information other than a destination URI to be passed in. Following is the full pseudo-schema of the MakeConnection element.
MakeConnection元素允许传入目标uri之外的其他标识信息。
The MakeConnection element allows for other identifying information other than a destination URI to be passed in. Following is the full pseudo-schema of the MakeConnection element.
MakeConnection元素允许传入目标uri之外的其他标识信息。
应用推荐