Context
The context attribute is an optional
attribute that can be included in event handlers to access various levels
of blips associated with the event blip itself. Think of
context as a blip-level configuration that allows you
to limit or expand the objects sent with the event.
To specify context, you add one or more context
attributes as parameters to the register_handler event. For example, the
following code will include sibling and parent blips (as well as the event
blip) when the ParticipantsAdded event is triggered:
myrobot.register_handler(events.ParticipantsAdded, context = event.Context.SIBLING + event.Context.PARENT)
Currently five case-insensitive context attributes are available:
PARENTSend the parent of the event blip out.
SIBLINGSSend the siblings (i.e., blips at the same level in the reply hierarchy as the event blip).
CHILDRENSend the children of the blip out.
SELFSend the blip itself.
SELFis always sent out. However, if nothing is specified in the context tag, the default ofPARENT+CHILDREN+SIBLINGS+SELFis sent out.SELFcan be used to send only the event blip.ALLDo a recursive complete scan, and send out all blips in the wavelet (but not the blips of any private replies—these reside in different wavelets).
You can use context to limit the amount of objects passed to your robot with an event, thereby reducing the load on your robot, or you can ask for all the blips if you want to get the full context of a wavelet.[41]