home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
Webinterface plugin
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="samuel337" data-source="post: 17808" data-attributes="member: 10347"><p>This is possible, even now. The web service already exposes most of the TV database functions from MP. However, there is an inevitable performance hit when first MP has to get the data from the database, then serialise it for the web service, then PHP has to interpret the XML, and finally it has to build the pages.</p><p></p><p>Of course, you could argue that you could use COM to interface with PHP, eliminating the web service middleman, but then there needs to be a common interface between the two technologies, which will most likely be XML, so again, you have performance hits when PHP has to intrepret the XML data.</p><p></p><p>Ultimately, the best case scenario would be to have the web interface in ASP.NET, however, due to legacy reasons, it is not and will most likely not be. The primary reason is that more people who are will to help seem to know PHP, and it also gives those who don't know a .NET language the chance to help out with the project.</p><p></p><p>Sam</p></blockquote><p></p>
[QUOTE="samuel337, post: 17808, member: 10347"] This is possible, even now. The web service already exposes most of the TV database functions from MP. However, there is an inevitable performance hit when first MP has to get the data from the database, then serialise it for the web service, then PHP has to interpret the XML, and finally it has to build the pages. Of course, you could argue that you could use COM to interface with PHP, eliminating the web service middleman, but then there needs to be a common interface between the two technologies, which will most likely be XML, so again, you have performance hits when PHP has to intrepret the XML data. Ultimately, the best case scenario would be to have the web interface in ASP.NET, however, due to legacy reasons, it is not and will most likely not be. The primary reason is that more people who are will to help seem to know PHP, and it also gives those who don't know a .NET language the chance to help out with the project. Sam [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Webinterface plugin
Contact us
RSS
Top
Bottom