Apologies if this has already been thought of/discussed. But it seems to be much of the behavior of the server is controlled by the clients.db file, which determines what the client devices expect and what their capabilities are. It also seems Twonky have to currently make a new release just to send out a clients.db.
Wouldn't it be smarter, if the server itself could check and optionally download a newer clients.db if one is available on the web.
Obviously i'm not a Twonky engineer and without indepth knowledge of what goes on, there may be more to it than this, but if it's possible, this could be a neat way of deploying support for new clients and client detection bugfixes quickly. (I know my Noxon and my PS3 have changed their UPnP identification string in the past without notice, and I had to wait for the clients.db to catch up before things worked correctly again.
Idea for improvement.
-
mgillespie
- Posts:1222
- Joined:Fri Jul 08, 2005 1:19 pm
- AV Hardware:TwonkyMedia AV UPnP Mediaserver (Marvell Kirkwood ARM Sheevaplug with Debian Squeeze).
2x Noxon V2 audio client
1x PS3 Slim 500GB Audio/Video UPnP client.
1x Sony VGF-CP1 Wireless Photoframe. - Location:UK
Please note: Moderators here are voluntary and do not work for PacketVideo or Twonky, please do not attack us. Any posts are personal opinion, and may not be those of PV/Twonky.