On Wed, September 27, 2006 11:07 am, Niklas Edmundsson wrote: > In practice this isn't enough when dealing with large files, so in our > production code (the hideously large jumbopatch) this is fixed by > read-while-caching and spawning a thread to do the caching in the > background while delivering the response (by read-while-caching) to > the client that initiated the caching.
A thread makes sense for platforms that support threads, but we would need some kind of functional behaviour for platforms that don't have threads. Would the option of spawning a process to copy the file also work, leaving the original process to read-while-cache the response for the benefit of the client? Regards, Graham --
