You can leave sensible defaults, but then you'd need to include some
sort of DENY / ACCEPT logic for people to override (mostly for
completeness).
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Jesse Kuhnert wrote:
I like that one as well. A compiled regexp pattern for each unprotected
resource spec will also help the possible performance hits.
I guess in the interest of configurability tapestry won't be able to have
anything unprotected by default, except perhaps for those resources tapestry
itself uses.
Does anyone see a need to ever protect css/js/image files like this? I'd
like to make everything as configurable as possible, but if this config spec
starts to grow unwieldy that wouldn't be pleasant either.
I'll leave everything protected for now..
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
