Reply to thread

Message

<blockquote data-quote="styrsven" data-source="post: 1176760" data-attributes="member: 135607">I looked at the code, and there is code for 4TR and the old API, but the api from 2.3 is different and not backward compatible, so LatestMediaHandler gets no contact.I actually downloaded the code and had a look.It seems to me that LatestTVRecordingsHandler.cs, Latest4TRRecordingsHandler.cs and LatestArgusRecordingsHandler.cs are copies of each other with minor changes in each.My attempt on doing something would be to create a common baseclass that all inherits from and just keep the server-specific code in the inherited classes (that would simplify LatestTVAllRecordingsHandler.cs also), Then creating a new class, LatestArgusPost23RecordingsHandler.cs for the new API.One issue is that the class for fetching the logo path is not a part of the published api, and only exist in a .NET4.5 dll.I could make an attempt to doing something like this if it is ok with you. It would probably take some time, though.</blockquote>

[QUOTE="styrsven, post: 1176760, member: 135607"] I looked at the code, and there is code for 4TR and the old API, but the api from 2.3 is different and not backward compatible, so LatestMediaHandler gets no contact. I actually downloaded the code and had a look. It seems to me that LatestTVRecordingsHandler.cs, Latest4TRRecordingsHandler.cs and LatestArgusRecordingsHandler.cs are copies of each other with minor changes in each. My attempt on doing something would be to create a common baseclass that all inherits from and just keep the server-specific code in the inherited classes (that would simplify LatestTVAllRecordingsHandler.cs also), Then creating a new class, LatestArgusPost23RecordingsHandler.cs for the new API. One issue is that the class for fetching the logo path is not a part of the published api, and only exist in a .NET4.5 dll. I could make an attempt to doing something like this if it is ok with you. It would probably take some time, though. [/QUOTE]

Verification