Brian This was actually how the original implementation worked and was later changed because we needed to ability to associate rewritten content with the cacheable version of the request and not the executed version of the request. See the OAuth and signing fetchers for examples of why this is important. Having the chained-fetchers do this just spreads the cache lookups throughout the code which isnt very DRY. A potential refactoring would be to allow for injecting cache entry pre/post processors into the cache.
-Louis On Fri, Jul 11, 2008 at 11:31 AM, Brian Eaton <[EMAIL PROTECTED]> wrote: > Hey - > > I just discovered the content rewriting logic in AbstractHttpCache. > I'm not going to mess with it right now, but I wanted to test the > waters: how do people feel about making the content rewriting part of > the content fetching chain instead of burying it down in caching > logic? > > I see that Kevin has considered moving this into gadget rendering: > https://issues.apache.org/jira/browse/SHINDIG-398. > > Cheers, > Brian >
