Reply to thread

Message: <blockquote data-quote="Koen Zomers" data-source="post: 677594" data-attributes="member: 108135"><p>Thanks for your extensive and clarifying post, bodiroga! I'm already <a href="https://forum.team-mediaportal.com/tv-server-plugins-294/whats-happening-hometvserver-mce-client-tv-server-82442/index3.html#post677587" target="_blank">in contact</a> with Mike Lowrey and KayDiefenthal on the Windows Media Center Plugin. As the matter of fact, that was my entry point to be involved in this Media Portal stuff. I was looking for a plugin for Media Center myself. As I began digging deeper into the information available on this forum, I found out the same as you are describing in your post.. many superb ideas, but totally uncoordinated and therefore lots of variations of stuff out there that is either half built or built too specifically for one goal. I just pulled some of the assemblies from Media Portal itself through Reflector and the base they offer looks quite nice. So in my opinion all there is to it is to create a very lightweight SOAP and/or REST wrapper around it and offer it to the mass to create client applications against. Whether this is to be a Windows App, Windows Service, Website App, Mobile App on whatever platform in whatever programming language, it doesn't matter since SOAP and REST are language independent standards. Based on my first impression this shouldn't be too much work. In my opinion all webservices that have been created so far are polluted with an overkill of samples and willing to be next-next-finish-ready. That should not be the goal for the webservice. There should not be a cassini webserver in it, there should not be a plugin in it, there should not be a webapplication in it. No! Just a webservice to roll out over an IIS farm which communicates with Media Portal. Any other fancy interfaces or stuff should be separate projects which communicate with the webservice.</p></blockquote><p></p>

Verification