<div class="gmail_quote">On Sun, Jan 22, 2012 at 6:11 PM, Philippe Marschall <span dir="ltr"><<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2012/1/22 Julian Fitzell <<a href="mailto:jfitzell@gmail.com">jfitzell@gmail.com</a>>:<br>
<div class="im">> Thinking totally off the top of my head, but what if it was implemented as a<br>
> filter? A few helper methods on WARequestHandler (or subclasses) could add<br>
> an instance if it's missing and then add the document and return a URL...<br>
<br>
</div>A filter on session? Yes that should work. That has the advantage that<br>
session doesn't first have the check whether the request is for a<br>
document handler. It also gives us a bit more parallelism because it's<br>
outside the session lock. Additionally you can override<br>
#initializeFilters and not add it if you don't need it. Registering<br>
the document handler gets a bit more complicated though because you<br>
have to find the right filter on session.</blockquote><div><br></div><div>Could be session or application in theory, but yeah, our distribution could set it up on session. Make the query key configurable and someone could put them anywhere. </div>
<div><br></div><div>That finding-a-filter thing really is a bit annoying... </div><div><br></div><div>Julian</div></div>