From OpenHome
(Difference between revisions)
(→Topology1) |
|||
Line 5: | Line 5: | ||
ohTopologyC is a software stack which provides a means of controlling devices, on a local network, via their UPnP service actions. It consists of a number of distinct layers. Each layer focuses on exposing specific properties and actions that are intended to be utilised by the layers above. Clients of ohTopologyC need only interface directly with the highest layer of the stack to gain access to the properties and actions exposed by the lower layers. | ohTopologyC is a software stack which provides a means of controlling devices, on a local network, via their UPnP service actions. It consists of a number of distinct layers. Each layer focuses on exposing specific properties and actions that are intended to be utilised by the layers above. Clients of ohTopologyC need only interface directly with the highest layer of the stack to gain access to the properties and actions exposed by the lower layers. | ||
- | == | + | ==Topology1 Classes== |
===Topology1=== | ===Topology1=== | ||
Line 11: | Line 11: | ||
- | == | + | ==Topology2 Classes== |
===Topology2=== | ===Topology2=== | ||
- | == | + | ==Topology3 Classes== |
===Topology3=== | ===Topology3=== | ||
- | == | + | ==Topology4 Classes== |
===Topology4=== | ===Topology4=== | ||
- | == | + | ==Topology5 Classes== |
===Topology5=== | ===Topology5=== |
Revision as of 09:21, 17 February 2015
ohTopology
Contents |
Overview
ohTopologyC is a software stack which provides a means of controlling devices, on a local network, via their UPnP service actions. It consists of a number of distinct layers. Each layer focuses on exposing specific properties and actions that are intended to be utilised by the layers above. Clients of ohTopologyC need only interface directly with the highest layer of the stack to gain access to the properties and actions exposed by the lower layers.