Niklas Edmundsson wrote:
* Realising that a file is a file and can be copied as such, without reading the whole thing into memory first. * When a file is cached by copying, replace the brigade with a new one refering to the cached file so we don't have to read the file from the backend again when sending a response to the client.
As I read the code, the copy is completed before an attempt is made to deliver the copy to the network. This should in theory stop a slow initial client from holding up faster following clients, if the caching is still "in transit".
Is this correct? Regards, Graham --
