Lines Matching refs:sequencer

25 they bind to an `lws_context`.  The sequencer callback may create
26 wsi which in turn are bound to a vhost, but the sequencer itself
31 The sequencer additionally maintains its own second-resolution timeout
36 The sequencer timeout operates separately and above any wsi timeout, and
37 is typically only reset by the sequencer callback when it receives an
41 If the sequencer timeout expires, then the sequencer receives a queued
46 Unlike lws timeouts which force the wsi to close, the sequencer timeout
49 `LWSSEQ_TIMED_OUT` is received, according to the state of the sequencer.
70 When created, in lws the sequencer objects are bound to a 'per-thread',
73 a user-specified callback which handles sequencer events
84 ## Queueing events on a sequencer
86 Each sequencer object can be passed "events", which are held on a per-sequencer
89 the sequencer's lifecycle, but otherwise the event indexes have a user-defined
90 meaning and are queued on the sequencer by user code for eventual consumption
91 by user code in the sequencer callback.
93 Pending events are removed from the sequencer queues and sent to the sequencer
101 Normally the sequencer callback receives a queued message that
104 `LWSSEQ_RET_DESTROY` from the sequencer callback.
109 actions... the lifecycle of the sequencer and the assets overlap but do not
110 necessarily depend on each other... that is a wsi created by the sequencer may
111 outlive the sequencer.
113 It's important therefore to detach assets from the sequencer and the sequencer
115 sequencer.  It doesn't necessarily mean closing the assets, just making sure
117 sequencer as its `.user_data`, when the wsi is out of scope for the sequencer
124 ## Watching wsi lifecycle from a sequencer
126 When a sequencer is creating a wsi as part of its sequence, it will be very
127 interested in lifecycle events.  At client wsi creation time, the sequencer
137 By receiving these, the sequencer can understand when it should attempt
140 When dealing with wsi that were created by the sequencer, they may close at
146 sequencer api `lws_sequencer_check_wsi()` which peeks the message