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 2
Plugin Development
Featured Plugins
UPnP / DLNA Media Server
UPnP / DLNA Media Server for MediaPortal 2
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="FreakyJ" data-source="post: 1155901" data-attributes="member: 106003"><p>Thank you very much for porting <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></p><p>It is actually different:</p><p>[CODE=XML]<Targets></p><p> <Target></p><p> android</p><p> </Target></p><p> </Targets>[/CODE]</p><p></p><p>MPExtended uses this to determine which client gets which profiles. You can request the Profiles by handing a "target" to MPExtended. Sure you can also retrieve android profiles e.g. for a webservice, but this is up to the developer if this makes sense.</p><p>By renaming this we don't get conflicts in case one just copies a profile from the DLNA Server to MP2Extended, because it gets just ignored.</p><p></p><p>Does that make sense? If not I am happy to change <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="FreakyJ, post: 1155901, member: 106003"] Thank you very much for porting :) It is actually different: [CODE=XML]<Targets> <Target> android </Target> </Targets>[/CODE] MPExtended uses this to determine which client gets which profiles. You can request the Profiles by handing a "target" to MPExtended. Sure you can also retrieve android profiles e.g. for a webservice, but this is up to the developer if this makes sense. By renaming this we don't get conflicts in case one just copies a profile from the DLNA Server to MP2Extended, because it gets just ignored. Does that make sense? If not I am happy to change :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Plugin Development
Featured Plugins
UPnP / DLNA Media Server
UPnP / DLNA Media Server for MediaPortal 2
Contact us
RSS
Top
Bottom