It would be great, Peter, if you guys could take the lead on formulating requirements and could float design ideas for this stuff. It really needs some focused thought.
As far as my comment regarding computational expense, I didn't mean to imply that we shouldn't consider ideas like Michael's. For lower-volume sites computational expense is less an issue than functionality. We just want to make sure we provide optional functionality that we know will scale well, too, and that we don't introduce computationally expensive features on a non-optional basis.
And acs-filters package? That's an interesting idea ...
