Re: Expose container type to external plugin (MediaServer2 dbus interface)

[Reinhold May <reinhold may gmx de>]

Quoting Jens Georg <mail jensge org>:

> Technically the client requests the sort-order and we have to fall-back
> to something if it doesn't.

Ah, I didn't know that.
My client of choice is BubbleUPnP. It offers only two choices with  
regard to sorting: Leave order as received from server and smart sort.

> dLeyna is a DLNA client implementation framework and they use
> MediaServer2 for server access. The extended documentation is available
> at https://01.org/dleyna/documentation/server-objects

I don't quite understand the reasoning of the dLeyna guys,  
specifically for the TypeEx property. Why introduce a new property  
that is a superset of Type? Because MediaServer2Spec is a standard and  
shouldn't be changed? Then increase the version of the standard. If  
there's a Type and a TypeEx property for virtually the same  
information what does a server do with conflicting information? What  
does another server do? The same or something different? This type of  
conflict resolution is not necessary.

But, maybe I'm missing the point.

Sorry for the rant, but please consider extending Type.