#6736: Improve Read's file transfer reliability
-----------------------------+----------------------------------------------
Reporter: cjb | Owner: morgs
Type: enhancement | Status: new
Priority: normal | Milestone: 9.1.0
Component: read-activity | Version:
Resolution: | Keywords: 8.2.0:- 9.1.0:?
Next_action: design | Verified: 0
Blockedby: | Blocking:
-----------------------------+----------------------------------------------
Changes (by morgs):
* priority: blocker => normal
* next_action: never set => design
* type: defect => enhancement
Comment:
Replying to [ticket:6736 cjb]:
> When someone joins a shared Read activity, they choose a peer to
download the shared file from at random (via a pop() of a python set),
rather than always choosing the person who originally started the sharing.
Might the person they choose this way not yet have finished downloading
the PDF themselves? What would happen in that case?
Peers only offer stream tubes once they have downloaded the file. Since
everyone offering it therefore completed the download (in theory) choosing
a random person is not necessarily worse than choosing the original
sharer.
The mechanism could be made more robust, like verifying the
download/transfer against a hash, assuming we don't gain a more reliable
file transfer.
Nevertheless, the current system (as of Read-50) does work, when the
network works, so I'm downgrading this priority.
--
Ticket URL: <http://dev.laptop.org/ticket/6736#comment:6>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system