> On 10/19/07, Philipp Koch <[EMAIL PROTECTED]> wrote: > > the way how the current "big" sling does spool static resources out of > > the repository is very nice and should somehow (as suggested by felix > > (kind of spool servlet) added to the micro sling "product" as well. > > 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. apache commons-io calls that: copy(InputStream, OutputStream) regards, toby -- -----------------------------------------< [EMAIL PROTECTED] >--- Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel T +41 61 226 98 98, F +41 61 226 98 97 -----------------------------------------------< http://www.day.com >---
