Invocation vs. request and response.
调用vs请求和响应。
Create an inline invocation human task.
创建内联调用人工任务。
This is the invocation of an operation.
这是对操作的调用。
This is known as the invocation pattern.
这被称为调用模式。
Respond to client invocation (as before).
响应客户机调用(与以前一样)。
The invocation pattern is the last pattern.
调用模式是最后一种模式。
Method: An invocation of a specific method.
方法：特定方法的调用。
Figure 3 shows the result of the invocation.
图3显示了调用结果。
Explicit invocation might occur anywhere.
显式调用可能发生在任何地方。
To support invocation from multiple protocols.
支持来自多个协议的调用。
Figure 2 shows the flow of service invocation.
图2显示了服务调用的流程。
You will now see the result of the invocation.
现在您将看到调用的结果。
Invocation: This one should be the most obvious.
调用：这应该是最明显的一个。
Server log after third time service invocation.
第3次服务调用后的服务器日志。
This invocation is modeled as a command pattern.
这种调用采用命令模式。
Third time invocation - response from the service.
第3次调用—来自服务的响应。
Asynchronous callback invocation breakdown view.
异步回调调用细分视图。
Create the dynamic invocation object from this service.
从此服务创建动态调用对象。
The three protocol invocation flows are shown in Figure 22.
三个协议调用流如图22中所示。
This model provides a much neater method invocation process.
这个模型提供了一个非常巧妙的方法调用过程。
You want to advise self-invocation in a transparent way.
你想要以透明的方式通知自调用。
Invocation task means that it can start the business process.
调用任务表示它可以启动业务流程。
The consumer can then choose the invocation model it likes best.
然后，使用者可以选择它最喜欢的调用模型。
There is still a long road left for dynamic invocation, however.
但是对于动态调用来说还有很长的一段路要走。
The asynchronous invocation pattern is highlighted in bold type.
异步调用模式以粗体突出显示。
Each separately called program is a program invocation instance.
每个被单独调用的程序就是一个程序调用实例。
It will then send a method invocation call to the remote server.
然后发送给远程服务器一个方法调用。
Using the new subject, the application makes the remote invocation.
应用程序使用新的主题进行远程调用。
After successful invocation, the following result page is displayed.
成功调用后，将显示以下结果页。
Class: the class where the method invocation, in context, belong to.
类：方法调用上下文所属的类。
应用推荐