Reply to thread

Message

<blockquote data-quote="thechad" data-source="post: 84622" data-attributes="member: 11382">The reason I was considering a web service to proxy the remoting commands to the TV server was the exact reason mentioned above that it is transported in binary and therefore I would not be able to use it with Python on the Xbox with out a lot of hassel.IIS has come a long way in version 6 and has been completely remodelled from previous versions so security should not be as big an issue as it was in earlier versions.&nbsp; That said I don't think we can use IIS as all the poor people out there running XP Home should not be stopped from running the web interface.Running a webserver with .Net in process is very easy and a basic unthreaed version can be written in less that 100 lines of code. Cassini is an advanced open version of this, see here for details <a href="http://http://msdn.microsoft.com/msdnmag/issues/04/12/ServiceStation/" target="_blank">http://msdn.microsoft.com/msdnmag/issues/04/12/ServiceStation/</a>I personally think that working with Asp.Net instead of PHP for the interface is the right choice due to the fact that the rest of MP is C# .Net and the fact that you can code Asp.Net so rapidly. I have developed in both PHP (mostly v4) and Asp.net and Asp.net has it all won for custom controls through inheritance and ease of binding controls to data.Also running the webserver in process would mean that we have easy control over it form within MP and would make installation a cake walk compared to the current MPW install.Anyway there my thoughts please continue with this discussion as I think we may ne onto something here.</blockquote>

[QUOTE="thechad, post: 84622, member: 11382"] The reason I was considering a web service to proxy the remoting commands to the TV server was the exact reason mentioned above that it is transported in binary and therefore I would not be able to use it with Python on the Xbox with out a lot of hassel. IIS has come a long way in version 6 and has been completely remodelled from previous versions so security should not be as big an issue as it was in earlier versions. That said I don't think we can use IIS as all the poor people out there running XP Home should not be stopped from running the web interface. Running a webserver with .Net in process is very easy and a basic unthreaed version can be written in less that 100 lines of code. Cassini is an advanced open version of this, see here for details [URL="http://http://msdn.microsoft.com/msdnmag/issues/04/12/ServiceStation/"]http://msdn.microsoft.com/msdnmag/issues/04/12/ServiceStation/[/URL] I personally think that working with Asp.Net instead of PHP for the interface is the right choice due to the fact that the rest of MP is C# .Net and the fact that you can code Asp.Net so rapidly. I have developed in both PHP (mostly v4) and Asp.net and Asp.net has it all won for custom controls through inheritance and ease of binding controls to data. Also running the webserver in process would mean that we have easy control over it form within MP and would make installation a cake walk compared to the current MPW install. Anyway there my thoughts please continue with this discussion as I think we may ne onto something here. [/QUOTE]

Verification