Some of these premises overlap.
One option would be to switch from glob string matching to regexp,
but that would be significantly slower and would require a larger
changes to avoid frequent regexp compilations.
I agree with your reasoning, and would also argue that moving to regexp would
potentially break existing filters, as well as a big speed penalty. That’s why
I coded my initial implementation in C. If someone wants regexp filename
matching, they can just filter every page request and do the regexp in Tcl.
The implemented approach allows to specify in addition to a
(positive) match pattern (such as "foo*") optionally a negative match
pattern (such as ^*.*), which can be used to say "match which such
It’s a slightly weird pattern match syntax, but as it’s efficient and easily
implemented, I like it!
from what I’m understanding, implementing a
anything-without-an-extension-is-adp would be a filter like this?
ns_register_adp GET /*^*.*
Is that right?
Can you confirm a file name of "test.situation.adp" would work with this
filter?
i.e.:
http://localhost/test.situation
If not, that’s an ok limitation, but I wanted to call it out.
-john
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
