可以根据需要灵活选择使用全局处理程序或者对每一个节点使用不同的处理程序完成这项工作。
And you can do this with the flexibility of using a global handler or a different one on each node as you see fit.
这可以通过在信号处理程序代码中设置一个全局标志并在完成关键部分的代码之后检查这个标志来实现。
This can be achieved by setting a global flag in the handler code and checking for the flag after completion of the critical part.
使用事件处理程序的索引来从全局输入列表中选择输入值。
Use the event handler’s index to select the input out of the global input list.
除预先定义的阶段和处理程序集外，用户还可以在操作级别、服务级别或全局级别配置用户阶段和相关处理程序。
In addition to the set of predefined phases and handlers, users can configure user phases and associated handlers at the operation, service, or global level.
如果没有局部变量，所有事件处理程序实例都将在相同的全局变量实例上工作。
Without local variables, all event handler instances would work on the same global variable instances.
完成此任务后，对全局计数器进行递减操作（该计数器对活动事件处理程序实例进行计数）。
Once that’s done, decrement the global counter that counts the number of active event handler instances.
只有事件处理程序完成了其业务逻辑后，它才会更新全局变量result，以将结果返回到MainScope。
Only when the event handler has finished its business logic, it updates the global variable result in order to return the result to MainScope.
发生这种情况是因为在 sess_write()会话处理程序中无法使用全局用户对象。
This happens because the global user object is not available in the sess_write() session handler.
与Axis 1. x处理程序链相比，使用模块的优势在于，您可以在根本不改变全局配置文件的情况下添加新模块。
The advantage with module over Axis 1.x handler chain is that you can add a new module without changing any global configuration files at all.
如果全局范围要求使用事件处理程序的结果，请在全局结果变量中设置该结果。
If the global scope requires the result of the event handler, set the result in the global result variable.
例如，客户机应用程序可以使用SQL和结果集逻辑把VSAM或IMS数据读取到全局或声明的临时表中，然后处理它们。
For instance VSAM or IMS data can be retrieved into a global or declared temporary table and subsequently processed by client applications using SQL and result set logic.
尤其是，它将设置一个全局计数器，以对处于活动状态的事件处理程序进行计数；另外，还要设置一个变量，以在列表中保存事件处理程序的结果。
Especially, it sets up a global counter that counts the number of active event handlers as well as a variable that holds the results of the event handlers in a list.
这些处理程序可以注册为全局、服务或操作作用域，并且最终的处理程序链将通过结合所有作用域的处理程序得出。
These handlers can be registered in global, service, or operation scope, and the final handler chain is calculated by combining the handlers from all the scopes.
除了其他事情外，它定义一个全局错误处理程序，在此将放置在执行主应用程序逻辑之前要运行的特定于平台的代码。
Among other things, it defines a global error handler, and it is where you would place any platform-specific code to run before executing main application logic.
JSR- 109 1.3增加了以下支持：单例会话bean作为端点，JAX - WS处理程序和端点中的CDI，以及全局、应用程序和模块命名上下文。
JSR-109 1.3 adds support for singleton session beans as endpoints, as well as for CDI in JAX-WS handlers and endpoints, and for global, application, and module naming contexts.
这将指示WebSphere运行时处理接收的任何WS-AT上下文，并在外部请求程序协调的全局事务下分派应用程序组件。
This instructs the WebSphere runtime to process any received WS-AT context and dispatch the application component under a global transaction that is coordinated by the external requester.
就是说，全局变量的值丢失并且事件处理程序被解除挂钩，这意味着以前在事件发生时执行的代码不再这样做了。
That is, the values of global variables are lost and event handlers are unhooked, meaning that code that formerly executed when an event occurs no longer does so.
你可以像处理应用程序规则一样，添加改变移除全局规则。
You can add, modify and remove global rules the same way as with application rules.
全局系统钩子是一个系统钩子，当指定的一些消息被系统中任何应用程序所处理时，这个钩子就被调用。
A global system hook is a system hook that is called when the specified messages are processed by any application on the entire system.
全局系统钩子是一个系统钩子，当指定的一些消息被系统中任何应用程序所处理时，这个钩子就被调用。
A global system hook is a system hook that is called when the specified messages are processed by any application on the entire system.
应用推荐