However, it is possible to support other protocols for service invocation.
然而，为了服务调用它可能还支持其他的协议。
To support invocation from multiple protocols.
支持来自多个协议的调用。
The real invocation of the rule engine is delegated to a simple rule session.
规则引擎的真正调用会被分配到一个简单的规则会话中。
I provide these examples simply to show the format of a typical REST invocation.
我提供这些例子，只是为了展示典型REST调用的格式。
Class: the class where the method invocation, in context, belong to.
类：方法调用上下文所属的类。
It must be possible to determine that a service invocation has occurred.
必须能够确定已经发生了服务调用。
It will then send a method invocation call to the remote server.
然后发送给远程服务器一个方法调用。
The hello_message action in the controller class is available to clients for method invocation.
控制器类中的 hello_message 操作可用于客户机进行方法调用。
The one at the client side to make the invocation.
在客户端用于发出调用的事务。
Respond to client invocation (as before).
响应客户机调用(与以前一样)。
This is the invocation point for the Client to the Axis engine.
这是Client调用Axisengine的位置。
In this case, we wish to use the deferred response invocation pattern described earlier.
在这种情况下，我们希望使用前面描述的延迟响应调用模式。
Service invocation technologies must be able to provide all of these security capabilities.
服务调用技术必须能够提供所有这些安全功能。
Such a setup would mean that each method invocation would be subject to indirection.
这样的设置将意味着，每个方法调用都会遭遇重定向。
You want to advise self-invocation in a transparent way.
你想要以透明的方式通知自调用。
Package: the package where the class and method invocation, in context, belong to.
包：类和方法调用上下文属于的包。
Events only allow to add and remove method from invocation list.
事件只允许在调用列表中添加和删除方法。
Events only allow to add and remove method from invocation list.
事件只允许在调用列表中添加和删除方法。
应用推荐