|
From: | Nala Ginrut |
Subject: | Re: [PATCH] read-response-body should return received data when any break happens |
Date: | Fri, 16 Mar 2012 10:23:53 +0800 |
On 16 March 2012 02:37, Ian Price <address@hidden> wrote:
> Daniel Hartwig <address@hidden> writes:Indeed. The procedure shown is similar to one from one of my own
>> For example, reusing the same bytevector and looping over
>> read-response-body! saving the results to disk each time. This limits
>> the memory use to the size of the bytevector *and* removes the copy
>> operation from your implementation (bonus!).
> If you wanted to do it that way, it'd be better to pass in the port
> directly and cut out the middle man.
>
projects which features the write-to-disk internally.
I guess it pays to keep in mind that it is trivial to rearrange
procedures such as this to suit any particular situation. The OP
appeared--to me--to be very over worked for the task.
Perhaps such error-tolerance/streaming capabilities can be tied in at
a level closer to get-bytevector-n...
Regards
[Prev in Thread] | Current Thread | [Next in Thread] |