Reply to thread

Message

<blockquote data-quote="MrTechno" data-source="post: 1064259" data-attributes="member: 111518">OK, long answer.Thanks to the way @[USER=97484]Oxan[/USER] designed the MPExtended architecture each of the functional groups (music, playlists, series etc) is written as a plugin to connect the web API to the backend. That means there's nothing to stop someone writing plugins that implement the function groups by using MP2.So why not write the plugins? Well one issue is to do with limitations on how MP2 represents collections (albums, artists, series) which makes even simple functions like an album count are tricky to implement. There's an ongoing MP2 dev debate about how to support these things but whatever is decided would mean reworking any code written now. The other issue is to do with performance and app structure. MPExtended runs as a service and the plugins run inside it, so the MP2 plugins would act like an MP2 client talking to the server over UPnP. A more performant way to do it would be to integrate the plugins into the MP2 server but MPExtended uses WCF to give it a web container and MP2 has a built in one which doesn't support the web API features. There's talk of switching MP2 server to OWIN but that would mean rework as well.All of which means unless someone is working on this in secret and doesn't mind working on it a lot more in the future I'm afraid using aMPdroid in MP2 is going to be while.</blockquote>

[QUOTE="MrTechno, post: 1064259, member: 111518"] OK, long answer. Thanks to the way @[USER=97484]Oxan[/USER] designed the MPExtended architecture each of the functional groups (music, playlists, series etc) is written as a plugin to connect the web API to the backend. That means there's nothing to stop someone writing plugins that implement the function groups by using MP2. So why not write the plugins? Well one issue is to do with limitations on how MP2 represents collections (albums, artists, series) which makes even simple functions like an album count are tricky to implement. There's an ongoing MP2 dev debate about how to support these things but whatever is decided would mean reworking any code written now. The other issue is to do with performance and app structure. MPExtended runs as a service and the plugins run inside it, so the MP2 plugins would act like an MP2 client talking to the server over UPnP. A more performant way to do it would be to integrate the plugins into the MP2 server but MPExtended uses WCF to give it a web container and MP2 has a built in one which doesn't support the web API features. There's talk of switching MP2 server to OWIN but that would mean rework as well. All of which means unless someone is working on this in secret and doesn't mind working on it a lot more in the future I'm afraid using aMPdroid in MP2 is going to be while. [/QUOTE]

Verification