| Noteinfo | ||
|---|---|---|
| ||
The Node pico engine only supports the alternate encoding at this time. |
...
The following key-value pairs are used:
| key | value | required? |
|---|---|---|
| _domain | the event domain | yes |
| _type | the event type. | yes |
| _async | raise the event asynchronously | no |
| _epi | endpoint identifier | no |
| _epl | endpoint location | no |
| _rids | a semicolon delimited list of ruleset identifiers. When the RID list is not specified, KRE fires any rule that is salient for the given event domain and type. | no |
| _timestamp | the timestamp for the event, if different than the time the ESL is called | no |
Keys with a leading underscore are reserved. Attributes are encoded as key-value pairs in the usual way.
When sent as the body of an HTTP POST the attributes must be encoded using one of the methods shown in the following table. Note that the Content-Type header must be set to the appropriate mime-type for the event consumer to understand the message.
| encoding | mime-type |
|---|---|
| form | application/x-www-form-urlencoded |
| JSON | application/json |
If the body is JSON-encoded, the encoding should be a JSON object containing the keys and values as follows:
...
When events are processed synchronously, the results of the processing, either a JSON-encoded directive document or a JavaScript program is returned to the generator. Actions in KRL are responsible for creating the response.
...