Quote:
Originally posted by pod
The problem doesn't really have anything to do with how servers comminucate with clients or how clients talk to each other.
As someone noticed earlier, when a multisourcing OpenNAP client came out, the trick may be to request multiple file resumes (so other clients understand it), and break the download when a certain point is reached, so the blocks don't overlap. Voila, you have multisourcing in OpenNAP.
I think the problem is being able to tell whether two files on different clients are really the same file.
|
Either way you look at it more opennap clients need to support mulisource before it could happen. If it was that easy it would have been done on mass scale already. The clients have to communicate properly inorder for it to work this would mean adding several commands not to just the client but most likely the server as well.
Alot of clients use different decoders for reporting bitrates. But in the end the file size is still the same and the clients compare files for resume even if a different bitrate is reported. Makes me think that is not the problem.
