Reply to thread

Message

<blockquote data-quote="samuel337" data-source="post: 84327" data-attributes="member: 10347">Chris84:Yes its not very clear what the PHP files do - reason explained in previous post. To find out all that the web service is capable of, navigate to <a href="http://localhost:81/MPExtControlWS/service.asmx" target="_blank">http://localhost:81/MPExtControlWS/service.asmx</a> (replacing localhost with the name of your MP computer/IP address if you're using another computer).Also note that there is a new version of the web service available in the mp-webinterface SVN repository that implements a lot more too. If you want, I can cut and paste a list of all the functions available - data is returned in XML format so it should be pretty easy to use for anyone using any language.As for the dotnet component taking up a lot of memory, that's unfortunate as like Chris84, I like apache as you can configure it using a text file. I love IIS however, for its UI. So if I can get the best of both worlds, it'd be awesome. But that's the reason IIS is not used - its difficult to automate configuration. Whilst Khris you may be able to configure it easily, I'm sure its not as easy for others.I'll be looking into an alternative for the dotnet apache module soon - I'm thinking of implementing a small web server in the ECP2 plugin, so that the web service is hosted by .NET natively, instead of using apache as the middle-man. That should eliminate all the performance problems. Also note that the last time I checked, the apache dotnet module is not .NET 2.0 compatible (while the code I'm using is .NET 2.0) so I don't like the situation very much. It will change soon <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />Sam</blockquote>

[QUOTE="samuel337, post: 84327, member: 10347"] Chris84: Yes its not very clear what the PHP files do - reason explained in previous post. To find out all that the web service is capable of, navigate to [url]http://localhost:81/MPExtControlWS/service.asmx[/url] (replacing localhost with the name of your MP computer/IP address if you're using another computer). Also note that there is a new version of the web service available in the mp-webinterface SVN repository that implements a lot more too. If you want, I can cut and paste a list of all the functions available - data is returned in XML format so it should be pretty easy to use for anyone using any language. As for the dotnet component taking up a lot of memory, that's unfortunate as like Chris84, I like apache as you can configure it using a text file. I love IIS however, for its UI. So if I can get the best of both worlds, it'd be awesome. But that's the reason IIS is not used - its difficult to automate configuration. Whilst Khris you may be able to configure it easily, I'm sure its not as easy for others. I'll be looking into an alternative for the dotnet apache module soon - I'm thinking of implementing a small web server in the ECP2 plugin, so that the web service is hosted by .NET natively, instead of using apache as the middle-man. That should eliminate all the performance problems. Also note that the last time I checked, the apache dotnet module is not .NET 2.0 compatible (while the code I'm using is .NET 2.0) so I don't like the situation very much. It will change soon :D Sam [/QUOTE]

Verification