From OpenHome
(Difference between revisions)
m (moved OhNet-What to OhNet:What) |
|||
| Line 1: | Line 1: | ||
| - | {{nav_openhome_ohnet| | + | {{nav_openhome_ohnet|OpenHome Net - What is it?}} |
ohNet is a full UPnP stack. Ports exist for Linux and Windows (Mac is in progress). The public APIs are protocol independent and offered in C++, C#, C and JavaScript (Control Point only). | ohNet is a full UPnP stack. Ports exist for Linux and Windows (Mac is in progress). The public APIs are protocol independent and offered in C++, C#, C and JavaScript (Control Point only). | ||
Revision as of 09:46, 1 August 2011
ohNet is a full UPnP stack. Ports exist for Linux and Windows (Mac is in progress). The public APIs are protocol independent and offered in C++, C#, C and JavaScript (Control Point only).
UPnP services are presented as classes with actions appearing as functions and state variables appearing as member variables. These classes are referred to as proxies for users of the Control Point stack and providers for users of the Device stack.
Proxies and Providers are included for all OpenHome and UPnP AV services. If your application uses other services, ohNet includes a tool (ohNetGen) to generate proxies and/or providers from the service XML in any of the supported languages.