This shows you the differences between the selected revision and the current version of the page.
| ecs_tec:how_to_write_a_destination 2007/02/09 20:05 | ecs_tec:how_to_write_a_destination 2010/07/19 14:32 current | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| Destination SystemObjects send events out of the ECS, often in an asynchronous manner due to the nature of both the ECS and the nature of the receiving protocol. Because of the unpredictable arrival of events to the destination from within the source as well as the unpredictable rate of consumption of events via the external receiver, a Destination must be threaded. This is done by specifying the right parameter for the //setEventProcessor()// call in the local //setVars()// method. | Destination SystemObjects send events out of the ECS, often in an asynchronous manner due to the nature of both the ECS and the nature of the receiving protocol. Because of the unpredictable arrival of events to the destination from within the source as well as the unpredictable rate of consumption of events via the external receiver, a Destination must be threaded. This is done by specifying the right parameter for the //setEventProcessor()// call in the local //setVars()// method. | ||
| + | |||
| + | [[ http://www.online-casino-gaming.org/ | casino online]] | ||
| + | |||
| A Destination is responsible for converting an “event” in the EventGnosis’ proprietary, normalized Event format (basically a small XML document) and streaming it to the receiving external entity via its specific protocol. | A Destination is responsible for converting an “event” in the EventGnosis’ proprietary, normalized Event format (basically a small XML document) and streaming it to the receiving external entity via its specific protocol. | ||