[mpris] [RFC] MPRIS2 Release Candidate
Zeeshan Ali (Khattak)
zeenix at gmail.com
Mon Aug 9 22:54:40 CEST 2010
Hi,
2010/8/9 Rémi Denis-Courmont <rem at videolan.org>:
> Le lundi 9 août 2010 22:06:52 Zeeshan Ali, vous avez écrit :
>> Sorry to jump in the middle of this discussion but talking of new/better
>> D-Bus spe, I was wondering if its possible to add the following two
>> properties to Player interface:
>>
>> * mime-types: List of mime-types supported by the player
>> * protocols: List of protocols (e.g HTTP, RTSP etc) supported by the player
>
> Oh please no. This is never going to work.
It doesn't need to be perfect. :) Just better than no way at all of
knowing what player can possibly handle.
> This is too simplistic to really
> work: what extensions to the MPEG4 file format does this player handle?
If you want to go down that road, I'm all good with providing DLNA
profile names instead (they are very specific).
> Plus, the namespace would be a huge mess. Normally URI schemes and MIME types
> *MUST* be registered with IANA.
Why is that a MUST? And whats stopping us from registering the
needed/missing mime-types to IANA?
> For MIME types, vnd and prs are the only
> allowed exception. How do you handle things like say, V4L2 and DirectShow
> inputs? There are no standards for the URI format even.
We can agree on some 'standard' on our own. In short, this
information is needed for UPnP/DLNA use-case so If you want to support
that and think we need to solve this issue, please do suggest a better
solution.
--
Regards,
Zeeshan Ali (Khattak)
FSF member#5124
More information about the mpris
mailing list