. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 11.6. Extension points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . version of the ContextRequest Java class. 2.3.4. SENDING EVENTS USING THE CONTEXT SERVLET At the same time as you are retrieving the context, you can also directly send events in the ContextRequest object These interests will be accumulated in Apache Unomi on profiles to indicate growing interest over time for specific topics.These are freely defined and will be accepted by Apache Unomi without needing

documentation. We welcome tickets/PRs to improve its robustness and progressively make it ready for prime time. 1.1.7. MIGRATE FROM UNOMI 1.X To facilitate migration we prepared a set of scripts that will automatically using a request such as this one: 2.4.6. ADDING A RULE Rules are a powerful ways to react in real-time to incoming events. For example a rule could update a profile when a certain event comes in, either the rule-list command to display all the rules in the system and the rule-tail to watch in real-time which rules are executed. The rule-view RULE_ID command will let you view the contents of a rule

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.3. Extension points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . positively identified. Apache Unomi 1.1.x - Documentation - 3 1.1.4. SESSIONS A session represents a time-bounded interaction between a user (via their associated profile) and a Unomi-enabled application users can provided extensions in the form of plugins. 1.2.1. TYPES VS. INSTANCES Several extension points in Unomi rely on the concept of type: the extension defines a prototype for what the actual items