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
WebService and Mobile Access
Consolidate MediaPortal Web Applications
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="gemx" data-source="post: 622427" data-attributes="member: 26324"><p>That was exactly what i had in mind when creating MPWebServices.</p><p>The only goal it should reach was to have a simple webservice layer to access the tvserver functions and databases of MP and TvServer.</p><p>The WebApp itself was just meant to be a demo of how the webservices could be used.</p><p>So basically MPWebServices IS the MPWeb-Code layer you mentioned.</p><p>Just throw away the webapp and use IIS or Apache as WebServer and you have the basis <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p>So my proposal would be to do the following:</p><p>1) Throw away MPWebService's web app</p><p>2) Use Apache or IIS to host the webservices</p><p>3) Let iPimp and other WebApps use the WebServices of MPWebServices instead of their own implementations to control TvServer and access the MP and TvServer databases</p><p>4) Host iPimp and other WebApps on the same WebServer</p><p></p><p>That's it <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="gemx, post: 622427, member: 26324"] That was exactly what i had in mind when creating MPWebServices. The only goal it should reach was to have a simple webservice layer to access the tvserver functions and databases of MP and TvServer. The WebApp itself was just meant to be a demo of how the webservices could be used. So basically MPWebServices IS the MPWeb-Code layer you mentioned. Just throw away the webapp and use IIS or Apache as WebServer and you have the basis :D So my proposal would be to do the following: 1) Throw away MPWebService's web app 2) Use Apache or IIS to host the webservices 3) Let iPimp and other WebApps use the WebServices of MPWebServices instead of their own implementations to control TvServer and access the MP and TvServer databases 4) Host iPimp and other WebApps on the same WebServer That's it :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
WebService and Mobile Access
Consolidate MediaPortal Web Applications
Contact us
RSS
Top
Bottom