On Thu, 26 Jul 2007 23:20:50 -0300, Robert Zeigler <[EMAIL PROTECTED]>
wrote:
Asset service doesn't really need a configuration point here, imo.
You can already make contributions to services that would allow you to
implement this sort of content filtering.
I agree up to a point. It's a concern that almost all projects have, so
the framework could (and should) provide an easy way to solve, be it some
configuration point in AssetService or another dispatcher provided by
Tapestry.
Thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
