Reply to thread

Message

<blockquote data-quote="Albert" data-source="post: 896773" data-attributes="member: 67886">3. Why do you think you need to use different instances of ILocalizedDeviceInformation? Actually, this data contains the information about a device. This data is normally always the same, independent from the client. The only thing which can be adapted is: The data can (and will) be sent in different languages for clients of different locales.4. For me, it sounds as if you want to something which is against the idea of UPnP/AV. The idea is that a client (=control point) connects to a server (=device), not vice versa. You should not need to know anything about your client (=the TV which requests data from your device). But if you really want to get to know which devices are present in the network, yes, you can do that with the UPnP lib. Take a look at MediaPortal\Tools\UPnPTools\UPnPDeviceSpy.5. Do I understand it correctly that you have already implemented code using the UPnP library to make your TV request media items via the MP2's ResourceAccessModule? Originally, that ResourceAccessModule wasn't written for transferring media items to DLNA devices, but now, as you say it - you're right, why not. But the problem that the TV just breaks the connection and the ResourceAccessModule doesn't notice that - that might be a problem with our HTTP server which is used by the MP2 resource server. Actually, the HTTP server should notice the connection break and raise an exception which should make the ResourceAccessModule stop sending the file... If I have time, I'll check if that works correctly.</blockquote>

[QUOTE="Albert, post: 896773, member: 67886"] 3. Why do you think you need to use different instances of ILocalizedDeviceInformation? Actually, this data contains the information about a device. This data is normally always the same, independent from the client. The only thing which can be adapted is: The data can (and will) be sent in different languages for clients of different locales. 4. For me, it sounds as if you want to something which is against the idea of UPnP/AV. The idea is that a client (=control point) connects to a server (=device), not vice versa. You should not need to know anything about your client (=the TV which requests data from your device). But if you really want to get to know which devices are present in the network, yes, you can do that with the UPnP lib. Take a look at MediaPortal\Tools\UPnPTools\UPnPDeviceSpy. 5. Do I understand it correctly that you have already implemented code using the UPnP library to make your TV request media items via the MP2's ResourceAccessModule? Originally, that ResourceAccessModule wasn't written for transferring media items to DLNA devices, but now, as you say it - you're right, why not. But the problem that the TV just breaks the connection and the ResourceAccessModule doesn't notice that - that might be a problem with our HTTP server which is used by the MP2 resource server. Actually, the HTTP server should notice the connection break and raise an exception which should make the ResourceAccessModule stop sending the file... If I have time, I'll check if that works correctly. [/QUOTE]

Verification