User Tools

Site Tools


events-ids-references

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
events-ids-references [2018/12/10 15:02]
barryfp
events-ids-references [2019/04/05 07:25] (current)
barryfp [The Event Model]
Line 77: Line 77:
  
 Note that event sinks are single-threaded,​ such that multiple simultaneous events received at a sink are placed into a queue. Once the event sink returns from handling the first event in the queue, the event sink is called again for the second item, and so on. If an event queue becomes full due to the speed of events arriving exceeding the speed of events being handled, the event queue will drop any further events that arrive until more space becomes available. Note that event sinks are single-threaded,​ such that multiple simultaneous events received at a sink are placed into a queue. Once the event sink returns from handling the first event in the queue, the event sink is called again for the second item, and so on. If an event queue becomes full due to the speed of events arriving exceeding the speed of events being handled, the event queue will drop any further events that arrive until more space becomes available.
 +
 +Finally, each event sink can only have one copy of the same event registered from the same object instance. If the above example used the line ''​sinkevent MyEvents(a)''​ twice, Dana would ignore the second ''​sinkevent''​ command and the associated event sink would only fire once per event. To stop receiving a specific event from an object, we use the instruction ''​stopevent MyEvents(a)''​.
events-ids-references.1544472173.txt.gz ยท Last modified: 2018/12/10 15:02 by barryfp