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="Koen Zomers" data-source="post: 682201" data-attributes="member: 108135"><p>In my opinion we should keep the webservice easy and simple and not make the same mistake again to include all kind of side tools in the webservice. Those tools should be seperate projects which use the webservice to gather information regarding the Media Portal service. More functionality means more chances of instability means a crippled base framework and more possibilities of yet another webservice that will never be finished. Mike his first webservice release looks very promising in that. Please don't start about integrating this and that again <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>Mike, do you have a link to what MPCC is? Couldn't find anything via Google. I'm just starting to get to know the architecture behind MediaPortal, so I'm wondering why there needs to be transcoding for this webservice? Can't we just pick up the streams generated by MediaPortal itself? If the answer is that transcoding could be useful to provide a lower bitrate stream for mobile devices, again.. this should be a seperate project on its own which provides flexible transcoded streams.</p></blockquote><p></p>
[QUOTE="Koen Zomers, post: 682201, member: 108135"] In my opinion we should keep the webservice easy and simple and not make the same mistake again to include all kind of side tools in the webservice. Those tools should be seperate projects which use the webservice to gather information regarding the Media Portal service. More functionality means more chances of instability means a crippled base framework and more possibilities of yet another webservice that will never be finished. Mike his first webservice release looks very promising in that. Please don't start about integrating this and that again :) Mike, do you have a link to what MPCC is? Couldn't find anything via Google. I'm just starting to get to know the architecture behind MediaPortal, so I'm wondering why there needs to be transcoding for this webservice? Can't we just pick up the streams generated by MediaPortal itself? If the answer is that transcoding could be useful to provide a lower bitrate stream for mobile devices, again.. this should be a seperate project on its own which provides flexible transcoded streams. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
WebService and Mobile Access
Consolidate MediaPortal Web Applications
Contact us
RSS
Top
Bottom