From OpenHome
(Difference between revisions)
(→API docs) |
|||
| (8 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
{{nav_openhome_ohnet|ohNet - Developers}} | {{nav_openhome_ohnet|ohNet - Developers}} | ||
=== Overview docs === | === Overview docs === | ||
| - | * Control Point (PDF) [http://www.openhome.org/releases/ | + | * [http://www.openhome.org/releases/ohNet_ControlPointStack.pdf Control Point stack (PDF)] |
| - | + | * [http://www.openhome.org/releases/ohNet_DeviceStack.pdf Device stack (PDF)] | |
=== API docs === | === API docs === | ||
| - | * | + | * [http://www.openhome.org/build/nightly/docs/CppStd/ C++] |
| - | * C# [http://www.openhome.org/build/nightly/docs/ | + | * [http://www.openhome.org/build/nightly/docs/Cs/ C#] |
| - | * | + | * [http://www.openhome.org/build/nightly/docs/Java/ Java] |
| - | * | + | * [http://www.openhome.org/build/nightly/docs/Js/ JavaScript] |
| + | * [http://www.openhome.org/build/nightly/docs/C/ C] | ||
| - | ohNet is written using C++ with std::string replaced by special buffer classes. These buffer classes allow for more efficient use of memory at the cost of a steeper learning curve. Memory use benefits can be especially pronounced for the Device stack. | + | === Discussion === |
| + | [http://forums.openhome.org/forumdisplay.php?fid=5 Developer forum] | ||
| + | |||
| + | |||
| + | |||
| + | ohNet is written using C++ with std::string replaced by special buffer classes. These buffer classes allow for more efficient use of memory at the cost of a steeper learning curve. Memory use benefits can be especially pronounced for the Device stack. [http://www.openhome.org/build/nightly/docs/CppCore/ API docs] for this version of the stack are available but the buffer classes are intended for internal use of the library and are as such currently undocumented. | ||
Latest revision as of 14:23, 2 September 2011
Overview docs
API docs
Discussion
ohNet is written using C++ with std::string replaced by special buffer classes. These buffer classes allow for more efficient use of memory at the cost of a steeper learning curve. Memory use benefits can be especially pronounced for the Device stack. API docs for this version of the stack are available but the buffer classes are intended for internal use of the library and are as such currently undocumented.