|
dxd - dynax driver framework 3.0.1d223
cross platform open source driver development framework
|
a device that is an IOService of the registry, without a driver connection of its own - what a proxy device derives its identity and its properties from More...
Namespaces | |
| namespace | client |
| namespace | stream |
Classes | |
| struct | accept |
| class | app |
| service::app - Windows Service Windows services are essentially just a type of container for which startup conditions can be defined. The service interface does not support any additional communication. Communication between client and service are usually be implemented using Windows named pipes. More... | |
| class | device |
| the registry entry behind a device: its class, the bundle that provides it and every property it publishes More... | |
| class | driver |
| service driver interface class More... | |
| class | manager |
| a service as the control manager sees it: installed, started, stopped and removed from here, its state followed by the promoted below More... | |
| class | parser |
| the service control command line: install, start, stop, remove and run in the console, on a dx::service::manager of its own. Its settings live under HKLM\SOFTWARE\<id>, writable where the process is elevated More... | |
| struct | request |
| one message on the service's pipe: what is asked, what came back and the value it carries. Every setting a hosted device mirrors has its own id here, so a client's promoted reaches the service's device with one round trip More... | |
| struct | start_type |
| struct | state |
| the service states, start types and accepted controls by their SDK names - what a status is printed and a command line argument read as More... | |
a device that is an IOService of the registry, without a driver connection of its own - what a proxy device derives its identity and its properties from
service interface namespace
| (c) copyright 2009 dynamic acoustics e.U. | generated on |