Reply to thread

Message

<blockquote data-quote="Albert" data-source="post: 700968" data-attributes="member: 67886">AW: MediaPortal2 : uPNP, DNLA ?zicoz, to answer that, we need to make clear what an MP2 server is. The definition is like this: The MP2 server contains the MediaLibrary. There is only one MediaLibrary in a whole MP2 system and thus only one MP2 server. The ML is the database where all media of the whole system is stored. You can search and browse media using the ML. It should be clear why there can only be one ML in an MP2 system: Because 1) it doesn't really make sense to have multiple databases in a system and 2) it would need a very complicated logic if we distributed the media storage to multiple computers.That means, one ML and thus one server in a system. The MP2 server becomes the &quot;home server&quot; for an MP2 client as soon as the client attaches to it. Technically, there can be multiple MP2 servers in a subnet, but the home server is the one server a client is attached to and where all its client's media is cataloged.But you are not restricted on the number of computers which CONTAIN media. For example, you could have several file servers whose media files are accessed by the MP2 server via file shares. Or via UPnP/AV (when we have implemented it).MP2 clients can also host media (which means each client can have local shares which are accessible in the whole MP2 system). But client shares are only available during the runtime of a client, which is typically much shorter then the runtime of the MP2 server.</blockquote>

[QUOTE="Albert, post: 700968, member: 67886"] [b]AW: MediaPortal2 : uPNP, DNLA ?[/b] zicoz, to answer that, we need to make clear what an MP2 server is. The definition is like this: The MP2 server contains the MediaLibrary. There is only one MediaLibrary in a whole MP2 system and thus only one MP2 server. The ML is the database where all media of the whole system is stored. You can search and browse media using the ML. It should be clear why there can only be one ML in an MP2 system: Because 1) it doesn't really make sense to have multiple databases in a system and 2) it would need a very complicated logic if we distributed the media storage to multiple computers. That means, one ML and thus one server in a system. The MP2 server becomes the "home server" for an MP2 client as soon as the client attaches to it. Technically, there can be multiple MP2 servers in a subnet, but the home server is the one server a client is attached to and where all its client's media is cataloged. But you are not restricted on the number of computers which CONTAIN media. For example, you could have several file servers whose media files are accessed by the MP2 server via file shares. Or via UPnP/AV (when we have implemented it). MP2 clients can also host media (which means each client can have local shares which are accessible in the whole MP2 system). But client shares are only available during the runtime of a client, which is typically much shorter then the runtime of the MP2 server. [/QUOTE]

Verification