Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are two main differences, I would say: scope and organisation.</p> <p><strong>UPNP</strong>'s scope is limited to the upnp standards and protocols. As long as a device has the protocols done right, by upnp's behalf it is compatible. But that's not the whole truth, as we know. For instance the media may be incompatible. The result is that the end user expects the system to work, but it does not.</p> <p><strong>DLNA</strong> on the other hand does not concentrate to upnp standards, it places requirements to ALL standards that are being used. Upnp AV happens to be one of those standards, but included are others, for instance:</p> <ul> <li>media (ensuring media in devices is compatible, and devices recognise is media compatible instead of trying and failing)</li> <li>mediaservers (exact requirements to HTTP headers and timeouts)</li> <li>etc</li> </ul> <p>As an oeganisation, <strong>UPNP</strong> is essentially a collection of protocols, a number of people that are working in developing that protocol. <strong>DLNA</strong> on the other hand (like the name suggests) is an alliance of companies that saw that they need to do something that their devices start talking to eachother - without errors.</p> <p>A rough analogue to mobile phone world:</p> <ul> <li>UPNP: phone has correctly implemented GSM/3G stack</li> <li>DLNA: you can actually call from one phone to another and have a conversation :-)</li> </ul> <p>From this analogue you can assume that DLNA specs are more complex. They are.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload