A context id (for example, customer id) uniquely identifies a common set of events flowing through a stream.
上下文id(例如,客户ID)唯一地标识流经某个流的一组公共事件。
Create ECSEmitter — create an instance of ECSEmitter by specifying the events factory to use and, optionally, the new context id.
创建ECSEmitter——通过指定所用的事件工厂及新的上下文标识符(可选)来创建ECSEmitter实例。
It does not have a context ID.
这个规则没有上下文id。
The functions and filters are evaluated for events with the same context ID.
函数和筛选器的评估针对具有相同上下文id的事件进行。
Using a context ID demonstrated how the use of a context relationship can affect performance.
使用上下文ID小节介绍了上下文关系如何影响性能。
Gets the context ID of the associated activity.
获取调用方活动的上下文id。
Removes all tokens from the cache that match a given context ID.
移除缓存中与给定的上下文ID匹配的所有令牌。
Removes the token from the cache that matches a given context ID and generation.
移除缓存中与给定的上下文id和生成匹配的令牌。
Gets a collection of security context security token IDs that match a specified context ID.
获取与指定的上下文ID匹配的安全上下文安全令牌ID的集合。
Gets the security context security token ID that matches a specified context ID and generation.
获取与指定的上下文id和生成匹配的安全上下文安全令牌id。
Contexts are sets of Interaction sets related by an Intermediate Object field called a context ID.
上下文是通过名为context ID的中间对象字段关联在一起的一组交互集。
The context ID (for example, a customer reference number) is used to determine which events have a relationship.
上下文id(例如,客户咨询号)用于确定哪些事件与其他事件存在关系。
In our example, the SellAfterBuy policy USES a context ID that is a combination of the customer ID and the stock ID.
在我们的示例中,SellAfterBuy策略使用的上下文ID是客户ID和股票ID的组合。
Complex rules by definition have a dependency on previous events and will therefore always have a context ID defined.
根据定义,复杂规则依赖于先前的事件,因此通常为其定义了上下文id。
Complex rules by definition have a dependency on previous events and will therefore always have a context ID defined.
根据定义,复杂规则依赖于先前的事件,因此通常为其定义了上下文id。
应用推荐