Re: Original Xbox clients hacks

[Jens Georg <mail jensge org>]

Hi,

> Responding to myself since I've found out what was the problem. The 
> server server just sends "options" to the client, and it's up to the 
> client to decide and make use of whichever resource it finds
> suitable.
>
> The trick off invalidating the resource mime_type only works because
> the 
> Xbox 360 will seemingly make its decision on the mime_type and thus
> any 
> resource having incorrect/unsupported mime_type will be discarded.
>
> Reading xbmc4xbox code I've found that it will just take the very
> first 
> resource available for each item. Easy to do. I've also found that 
> xbmc4xbox doesn't always advertise itself as such: during browsing
> it 
> uses the User-Agent of its underlying library: platinium.

Yes, that's the usual behaviour of Kodi/XBMC since forever.

What I've done:
> -Client hack to make the MPEG_TS_SD_EU_ISO first in list
> -Try xbmc4xbox client hack before the XBox360 client hack to avoid
> conficts
> -Use the specific version of platinium in the agent string to avoid 
> conflicts with recent versions of Kodi.
>
> Here is the patch:

First, thanks for analyzing this and making a patch, much appreciated
:)

The Ususal way of submitting patches is bugzilla for better review and
tracking.

The "platinum" user agent also applies to the XBMC/Kodi hacks which
need some fiddling with mime-types, also I don't like that specific
version. Is there anything more distinct to the xbmc4xbox?