seanadams said: > We'd need to add some other machinery eg a TCP througput test or ping > test which the user would initiate.
It is usually fairly easy (a SMOP) for a client to record the effective incoming data rate. From that, and a little bit of knowledge about what the stream is (i.e. FLAC, so expect 70kb/s or low-res MP3, so expect 10kb/s) you can have the client know that it isn't being feed fast enough (altho it can also count dropouts due to buffer empty). So with two separate metrics, the client could tell a suitable server that this link is unlikely to work they way people want. Even suggest doing something to fix it, like transcoding to a lower rate, or using a wired connection, or turning off the microwave oven. The good part of this is that a lot of accuracy is not needed. You just want to know one or so significant digit. Pat http://www.pfarrell.com _______________________________________________ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/beta
