Difference between revisions of "Developer:Davaar"
(→Services) |
(→Services) |
||
Line 30: | Line 30: | ||
* [[Developer:Davaar:AvtService|UPnP AV Transport Service]] | * [[Developer:Davaar:AvtService|UPnP AV Transport Service]] | ||
* [[Developer:Davaar:RenderingControlService|UPnP Rendering Control Service]] | * [[Developer:Davaar:RenderingControlService|UPnP Rendering Control Service]] | ||
− | |||
* [[Developer:Davaar:RadioService|Radio Service]] | * [[Developer:Davaar:RadioService|Radio Service]] | ||
* [[Developer:Davaar:InfoService|Info Service]] | * [[Developer:Davaar:InfoService|Info Service]] |
Revision as of 12:31, 23 November 2010
Contents
Davaar Developer Documentation
Overview
Davaar is the name of a Linn software compatibility family. It represents a family of on- and off-device software that is interoperable.
This interoperability consists in a stable set of well-defined interfaces and a shared set of software practices, including product discovery and playlist management algorithms.
Davaar contains two headline features:
- Openhome compatibility
- Party mode support
Openhome compatibility
Openhome is an independent standard for networked home devices. Davaar brings Linn's DS devices into line with this Openhome standard. Each Openhome service is described below together with a migration guide for its Linn Cara equivalent.
Party mode support
Davaar allows one DS to play whatever is being played by another DS. This is achieved by coupling the new Receiver source (and associated service) with the new Sender service. A detailed description is given below.
Davaar 1
Davaar 1 develops upon some of the ideas that began to become established in Cara. It differs from Cara...
Services
- Product Service
- Playlist Service
- Jukebox Service
- UPnP AV Transport Service
- UPnP Rendering Control Service
- Radio Service
- Info Service
- Time Service
- Volume Service
- Sender Service
- Receiver Service
Algorithms
Known Issues
If you are using a alpha or beta release of the code, bugs, features and performance issues should be expected. Keeping an up-to-date bug log on this Wiki page would be unreasonable, hence only issues which require a work-around to get the code running will be listed here in detail.
Required Workarounds
- None