Quote:
Originally Posted by chaley
The mechanism is the same as used for streaming online content. The "source" app, in this case CC, gives the "sink" app, in this case the reader, a "handle" to the data. The handle permits the sink to get the data serially from the source, copying it over a potentially internal network. If there is no possibility of moving backwards in the data or requiring access some time later then the sink can process the data stream without making a copy. If the sink must support replay, repositioning, or device restart then it must copy the data to a file it controls before permitting the user to access the data.
It would be very easy for the sink to end up with multiple copies of the same thing.
|
Ugh, of all the things to copy from iOS, why did Android copy the inane file handling?
