Reply to thread

Message: <blockquote data-quote="henso" data-source="post: 896456" data-attributes="member: 119106">What a mess... I told you I have no experience with UPnP.... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" />When I say device I mean the physical device like a TV, XBox, PS3 or whatever. 3. In the MP2 server there's an interface called ILocalizedDeviceInformation which content is what is sent to the TV when it requests it from the MP2 server. I need to be able to send different ILocalizedDeviceInformation depending on which TV type is requesting the information. The method DvDevice:AddDeviceDescriptionsRecursive is responsible for sending the ILocalizedDeviceInformation information using the property _deviceInformation. So I need to be able to override _deviceInformation depending on what TV type is connecting.4. This is just something I read about, so what I think I need is being able to request the TV's ILocalizedDeviceInformation somehow. I believe this can be done by sending an M-SEARCH to the TV and waiting for it to respond. Is this possible with the current UPnP classes in MP2?5. The MP2 server is using an IResourceServer interface to to listen for file requests. The TV reads the content library info from the MP2 server over DLNA. Inside this info are HTTP links used to access the file (like <a href="http://MP2ServerIP:Port/GetDlnaResource/MediaItemGuid" target="_blank">http://MP2ServerIP:Port/GetDlnaResource/MediaItemGuid</a>). The TV then downloads the file stream using this link which is established using a client (HTTP client) connection to the MP2 resource server (HTTP server). If the TV then stops playing the file it will disconnect this client from the MP2 resource server. So the streaming part has nothing to do with UPnP. The problem is that in the HTTP module used for streaming the file there is no indication that the TV is no longer connected and therefore it keeps streaming to a client that is no longer connected.</blockquote>

Verification