Connection and Disconnection Events
Assuming no failures occur during setup, the first event type each block receives
is NvSciStreamEventType_Connected
. This indicates that the block has a
complete connection path to the producer and consumers, respectively. After connecting, no
operations are allowed on any block until this event is received. Applications must wait
for it before proceeding with the resource setup described in the next section.
If a block is destroyed, an NvSciStreamEventType_Disconnected
event is
sent to connected blocks. If other events are pending, such as available payloads, they are
processed first. Once this event is received, no further events arrive, and operations to
send events fail.
In safety-certified systems, failures and teardown are never supposed to occur. Although disconnect events are currently supported in the current safety release, they will be removed in later safety releases, and only supported for non-safety platforms.