Lumiera
0.pre.03
»edit your freedom«
|
#include "vault/gear/scheduler-frontend.hpp"
Access point to the scheduler service provided by the back-end.
Steam-Layer uses this service as the primary means of instructing the vault; suitably prepared and wired frame render jobs are handed over to the scheduler for time-bound or bandwidth-controlled execution
this is planned to become the frontend to the render node network, which can be considered at the lower end of the middle layer; the actual render operations are mostly implemented by the vault layer
define the low-level scheduler interface and hook in the necessary calls to implement this frontend. ////////TODO WIP as of 9/2013
Definition at line 58 of file scheduler-frontend.hpp.
Public Member Functions | |
JobTransaction | startJobTransaction () |
Static Public Attributes | |
static lib::Depend< SchedulerFrontend > | instance |
access point to the Engine Interface. More... | |
Classes | |
class | JobTransaction |
Definition context for jobs to be scheduled. More... | |
Friends | |
class | SchedulerDiagnostics |
Protected Member Functions | |
void | activateTracing () |
Switch the complete engine into diagnostics mode. More... | |
void | disableTracing () |
EX_FREE. | |
|
protected |
Switch the complete engine into diagnostics mode.
This activates additional logging and reporting facilities, allowing to verify some specific operations within the engine did indeed happen. Activating this mode incurs a performance hit.
Definition at line 42 of file scheduler-frontend.cpp.
|
static |
access point to the Engine Interface.
storage for the (singleton) scheduler access frontend
this is an facade interface for internal use by the player. Client code should use the Player.
Definition at line 65 of file scheduler-frontend.hpp.