Lines Matching full:leader

372 - **Port Leader:** A Port Leader is the APL object which caused the creation
376   In the simple client API, the QCSO is the port leader.
377   In a client using a QLSO, the QLSO is the port leader.
378   In a server, the QLSO is the port leader.
380 - **Event Leader:** An Event Leader is the APL object which handles event
382   equivalent to a call to SSL_handle_events() on the Event Leader, which handles
385   The event leader is the highest-level APL object in a QUIC APL object
388   In the simple client API, the QCSO is the event leader.
389   In a client using a QLSO, the QLSO is the event leader.
390   In a server, the QLSO is the event leader.
392 - **Domain:** A QUIC domain is a set of APL objects rooted in an Event Leader.
394   are channeled up to the Event Leader and processed there. A QUIC domain is a
411 Leader and Domain Leader concepts going forward:
416 QDSO (QUIC_DOMAIN/QUIC_ENGINE)              Event Leader
417     QLSO (QUIC_LISTENER/QUIC_PORT)          Port Leader
425 QLSO (QUIC_LISTENER/QUIC_PORT)              Event Leader, Port Leader
431 Here we see that the QLSO now has the Event Leader role, as it is the most
434 Leader role, but the corresponding QUIC_DOMAIN APL object will not exist, as
440 QCSO (QUIC_CONNECTION/QUIC_CHANNEL)         Event Leader, Port Leader
446 Here we see that the QCSO now has the Port Leader role. Note that a QUIC_PORT
447 will be created internally to allow the QCSO to service the Port Leader role,
449 API-visible. Similarly a QUIC_ENGINE is spun up to handle the Event Leader role,