Reply to thread

Message

<blockquote data-quote="Albert" data-source="post: 631986" data-attributes="member: 67886">AW: MediaPortal 2 progress reportLater: Yes. At the first time: No.We are using the UPnP protocol for communication between client and server but we don't use the UPnP AV infrastructure.That means, to access a UPnP AV MediaServer at a NAS device, you need a special UPnP AV media provider, which can easily be implemented using the MediaPortal 2 plugin framework and thus will probably be implemented soon (either from the MediaPortal core team or from someone from the community).The other way around, the MediaPortal 2 server doesn't implement a UPnP AV compatible MediaServer service. But like for the client, this service can easily be implemented in a plugin.The MediaPortal 2 infrastructure provides many &quot;hooks&quot; for plugins to develop desired functionality. Plugins can simply add UPnP devices and services, plugins can add HTTP server modules (for example for remote management), plugins can provide access to media data over foreign protocols (for example by implementing the access over an FTP server etc.), plugins can implement media item metadata extractor code etc.So if some required functionality isn't implemented by the MediaPortal core team, it is easy for plugin devs to enhance the functionality.</blockquote>

[QUOTE="Albert, post: 631986, member: 67886"] [b]AW: MediaPortal 2 progress report[/b] Later: Yes. At the first time: No. We are using the UPnP protocol for communication between client and server but we don't use the UPnP AV infrastructure. That means, to access a UPnP AV MediaServer at a NAS device, you need a special UPnP AV media provider, which can easily be implemented using the MediaPortal 2 plugin framework and thus will probably be implemented soon (either from the MediaPortal core team or from someone from the community). The other way around, the MediaPortal 2 server doesn't implement a UPnP AV compatible MediaServer service. But like for the client, this service can easily be implemented in a plugin. The MediaPortal 2 infrastructure provides many "hooks" for plugins to develop desired functionality. Plugins can simply add UPnP devices and services, plugins can add HTTP server modules (for example for remote management), plugins can provide access to media data over foreign protocols (for example by implementing the access over an FTP server etc.), plugins can implement media item metadata extractor code etc. So if some required functionality isn't implemented by the MediaPortal core team, it is easy for plugin devs to enhance the functionality. [/QUOTE]

Verification