TsgcQUICClient › Events
Events you can handle, grouped by purpose, followed by the full alphabetical list.
| Name | Description |
|---|---|
| OnQUICConnect | Fires once the QUIC connection has been established and the client is ready to send data. |
| OnQUICDisconnect | Fires when the QUIC connection has been closed, reporting the close code and reason. |
| Name | Description |
|---|---|
| OnQUICStreamData | Fires with the bytes read from a QUIC stream. Inert until EnableMultiStream has been called. |
| Name | Description |
|---|---|
| OnQUICException | Fires when an exception is raised on the QUIC connection so the application can handle it. |
| Name | Description |
|---|---|
| OnQUICConnect | Fires once the QUIC connection has been established and the client is ready to send data. |
| OnQUICDisconnect | Fires when the QUIC connection has been closed, reporting the close code and reason. |
| OnQUICException | Fires when an exception is raised on the QUIC connection so the application can handle it. |
| OnQUICStreamData | Fires with the bytes read from a QUIC stream. Inert until EnableMultiStream has been called. |
Threading. The component sets NotifyEvents to neNoSync in its constructor, so every handler runs on the thread that raised it, not on the main thread. Marshal to the main thread before touching VCL or FMX controls.
Availability. OnQUICConnect, OnQUICDisconnect and OnQUICException are published and appear in the Object Inspector. OnQUICStreamData is public, so it can only be assigned in code, and it exists in the Delphi/C++Builder implementation only.