Idea for improvement.
Posted: Fri Apr 24, 2009 9:09 pm
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.
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.