systems. They interact with Unomi by providing raw, uninterpreted contextual data in the form of events and associated metadata. That contextual data is then processed by the context server to be fed to clients clients once actionable. In that sense context server clients are both consumers and producers of contextual data. Context server clients will mostly interact with Unomi using a single entry point called example will not make use of it. On the other hand, the cxs top level object contains interesting contextual information about the current user: { "profileId":

0 码力 | 32 页 | 477.20 KB | 1 年前

3

systems. They interact with Unomi by providing raw, uninterpreted contextual data in the form of events and associated metadata. That contextual data is then processed by the context server to be fed to clients clients once actionable. In that sense context server clients are both consumers and producers of contextual data. Context server clients will mostly interact with Unomi using a single entry point called example will not make use of it. On the other hand, the cxs top level object contains interesting contextual information about the current user: { "profileId":

0 码力 | 158 页 | 3.65 MB | 1 年前

3

systems. They interact with Unomi by providing raw, uninterpreted contextual data in the form of events and associated metadata. That contextual data is then processed by the context server to be fed to clients clients once actionable. In that sense context server clients are both consumers and producers of contextual data. Context server clients will mostly interact with Unomi using a single entry point called example will not make use of it. On the other hand, the cxs top level object contains interesting contextual information about the current user: We will look at the details of the context request and response