028e633af4
The 'Session_object' unifies several aspects of server-component implementations: * It keeps track of session quotas and is equipped with standardized interfaces (Quota_guard) to upgrade (and in the future potentially downgrade) session quotas in a uniform way. * It follows the pattern of modern RPC objects / signal handlers that manage/dissolve themselves at the entrypoint given as constructor argument. Thereby, the relationship with its entrypoint is always coupled with the lifetime of the session-component object. * It stores the session label, which was previously done manually by most but not all server-component implementations. * It stores the session 'diag' flag. * It is equipped with output methods 'diag', 'error', and 'warning'. All messages printed from the context of a session component is automatically prefixed with the session type and client label. Messages passed via 'diag' are only printed if the 'diag' flag of the session is set. Issue #2398 |
||
|---|---|---|
| .. | ||
| base | ||
| cap_session | ||
| cpu | ||
| cpu_session | ||
| cpu_thread | ||
| dataspace | ||
| deprecated | ||
| drivers | ||
| io_mem_session | ||
| io_port_session | ||
| irq_session | ||
| log_session | ||
| parent | ||
| pd_session | ||
| ram_session | ||
| region_map | ||
| rm_session | ||
| rom_session | ||
| root | ||
| session | ||
| spec | ||
| thread | ||
| trace_session | ||
| util | ||
| README | ||
This directory contains include files of interfaces that are exported by components to be used by other components. Each subdirectory corresponds to the component exporting the interface.