Hi, On 10/19/07, Tobias Bocanegra <[EMAIL PROTECTED]> wrote: > > What's the advantage of spooling here? Is it the performance > > improvement or are the functional benefits? In both cases I'd rather > > like to see the issues addressed by the underlying repository rather > > than by an extra layer of caching. > > where is no extra layer of caching here. by spooling we mean: read > from the input stream from the data of the repository, and write it to > the output stream of the response.
The use of "spooling" as a term is a bit confusing, see for example the Wikipedia definition (http://en.wikipedia.org/wiki/Spooling): In computer science, spooling refers to process of communicating data to another program by placing it in a temporary working area, where the other program can access it at some later point in time. I'd rather use "streaming" for the process of passing the data directly to the client without spooling (!) it first somewhere on disk or in memory. BR, Jukka Zitting
