Expand description
This module provides a high-level access to the server-side of Tango.
Structs§
- Attr
- An attribute of a single device, together with the last value written to it, which
Tango keeps aside from the model, and its configuration on that device. Its definition
is shared the way that of a
Commandis. - AttrDef
- A builder for defining an attribute of a device.
- Class
- A class of a server, through which its devices reach its definition and the properties the database holds for it.
- Class
Def - A builder for defining a device model and interface.
- Command
- A command of a single device, which is what the server runs when a client asks for it: one of its interface, around the definition it was defined with, or one of the three every device has whatever its class: the State, the Status and the Init.
- Command
Def - A builder for defining a command of a device.
- Dev
- The handle to a device from within its own execution functions, giving access to the device outside of its model.
- Server
- The context shared by the classes and the devices of a server, which every class of it
owns, and which reaches what owns them, its
Core, weakly. - Server
Args - The command line every server is launched with: the instance it runs as, how much it logs, and where it listens.
- Server
Builder - What a server is built with, and served by, see
Self::serve. - Server
Handle - The handle to a server being served, which is what owns it on behalf of its caller, and derefs to it.
Traits§
- Model
- What a device model has to be, gathering in one bound everything a server needs of it: it is shared between the threads serving the requests.
Functions§
- terminate
- Terminate the servers of this process that are stopped on termination, see
super::ServerBuilder::stop_on_terminate: those served are stopped, as theKillcommand of their admin device does, which deletes their devices, while those booting give up their boot, as does any served afterward.