XM DLINKTHUMB for d-link thumbnail support XM PHILIPSSRT for philips subtitle support XM PHILIPSSEARCH special handling for philips search DX REDSONIC for clients like DSM 520 which need the resonic string to enable nice UI DX WMC for clients which need a WMC compliant device description ![]() DX ABSOLUTEURI for clients which can not cope with relative URI path HP NETGEARRTP - support special Netgear RTP style HP 1.0RESPONSE - client requires 1.0 response on 1.0 request HP LIVEPSPLENGTH - special PSP header for live content HP LIVEWITHLENGTH HTTP protocol needs content length ![]() HP HTTP protocol option, chunked for chunked support, close for always close connection AV Audio/Video options - M for Music only HH HTTP Header field (user agent) of client. Here below is the client database from twonky … ![]() That is user agent string is then used to determine what kind of device is connecting to the server.Īs of I best know, twonky is using the standard upnp library like MT.Ĭould MT use this approach as well to identify clients ? I've been poking around in the twonkymedia files and I noticed aĬlient database lookup table that is used to identify renderers/clients based on the HTTP Header (user agent) that each client sends when it connects to the media server.
0 Comments
Leave a Reply. |