Reply to thread

Message

<blockquote data-quote="FreakyJ" data-source="post: 1154945" data-attributes="member: 106003">I can agree with this <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />If you take a look here: <a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/17_Extensions/Remote_Access/MPExtended/Developers/API_Documentation/MAS" target="_blank">http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/17_Extensions/Remote_Access/MPExtended/Developers/API_Documentation/MAS</a>The API has a Id's for seasons and Shows. MP2 doesn't really (yet). So if one requests all episodes for a season, I get the id for the Season item in M_MEDIAITEM.Now there is no link to the episodes, that's why I have to pars the name and than take the season number to get the episodes.And I think I just found a bug :/ Because it will return all episodes corresponding to a season number and not a special season.So I need to create my own ID:1) {seariesName<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused&nbsp; &nbsp; :confused:" loading="lazy" data-shortname=":confused:" />eason} -&gt; base642) {GUID-Seasies:GUID-Season}I think I will go with option two. I meant more DB requests, but I think it will have less errors, because GUIDs don't contain &quot;:&quot;, names could.Actually I use both. I called it MicroModules. and every Api part (e.g. GetTVEpisodeCountForTVShow ) has it's own micro module. And a lot of these use id's. That's why I put the GUID parsing in it's own function, but sometimes I also get the GUID from MP directly. I hope that makes sense <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />I use your method <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />[CODE=C#]{&quot;GetMediaItem&quot;, new GetMediaItem()},&nbsp; &nbsp; &nbsp; { &quot;TestConnection&quot;, new TestConnection()},&nbsp; &nbsp; &nbsp; // TvShow&nbsp; &nbsp; &nbsp; { &quot;GetTVEpisodeBasicById&quot;, new GetTVEpisodeBasicById()},&nbsp; &nbsp; &nbsp; { &quot;GetTVEpisodeCountForSeason&quot;, new GetTVEpisodeCountForSeason()},&nbsp; &nbsp; &nbsp; { &quot;GetTVEpisodeCountForTVShow&quot;, new GetTVEpisodeCountForTVShow()},&nbsp; &nbsp; &nbsp; { &quot;GetTVEpisodeDetailedById&quot;, new GetTVEpisodeDetailedById()},&nbsp; &nbsp; &nbsp; { &quot;GetTVEpisodesBasic&quot;, new GetTVEpisodesBasic()}[/CODE]It is like a Switch: I registered a HTTP module for MPExtened this module routes the request to the submodules: MAS, SAS, ?? depending on the second part of the URL, e.g. &quot;MediaAccessService&quot;.This module than sends the request depending on the last part of the url to one of the micromodules, it get's an answer (dynamic), parsis it with json and sends it to the client <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="FreakyJ, post: 1154945, member: 106003"] I can agree with this :) If you take a look here: [URL]http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/17_Extensions/Remote_Access/MPExtended/Developers/API_Documentation/MAS[/URL] The API has a Id's for seasons and Shows. MP2 doesn't really (yet). So if one requests all episodes for a season, I get the id for the Season item in M_MEDIAITEM. Now there is no link to the episodes, that's why I have to pars the name and than take the season number to get the episodes. And I think I just found a bug :/ Because it will return all episodes corresponding to a season number and not a special season. So I need to create my own ID: 1) {seariesName:Season} -> base64 2) {GUID-Seasies:GUID-Season} I think I will go with option two. I meant more DB requests, but I think it will have less errors, because GUIDs don't contain ":", names could. Actually I use both. I called it MicroModules. and every Api part (e.g. [SIZE=3][B]GetTVEpisodeCountForTVShow [/B]) has it's own micro module. And a lot of these use id's. That's why I put the GUID parsing in it's own function, but sometimes I also get the GUID from MP directly. I hope that makes sense :)[/SIZE] [SIZE=3]I use your method :)[/SIZE] [SIZE=3][CODE=C#]{"GetMediaItem", new GetMediaItem()}, { "TestConnection", new TestConnection()}, // TvShow { "GetTVEpisodeBasicById", new GetTVEpisodeBasicById()}, { "GetTVEpisodeCountForSeason", new GetTVEpisodeCountForSeason()}, { "GetTVEpisodeCountForTVShow", new GetTVEpisodeCountForTVShow()}, { "GetTVEpisodeDetailedById", new GetTVEpisodeDetailedById()}, { "GetTVEpisodesBasic", new GetTVEpisodesBasic()}[/CODE] It is like a Switch: I registered a HTTP module for MPExtened this module routes the request to the submodules: MAS, SAS, ?? depending on the second part of the URL, e.g. "MediaAccessService". This module than sends the request depending on the last part of the url to one of the micromodules, it get's an answer (dynamic), parsis it with json and sends it to the client :) [/SIZE] [/QUOTE]

Verification