Am 17.01.17 um 23:53 schrieb Stephen: >> That is a neat idea! The only disadvantage is, that the order of >> registration is important, >> which can can lead to fiddling with the config file and to some not easy >> predictable behavior. > Does it make any difference in practice? Don't know. The config files are designed having separation of concerns in mind, the plain NaviServer user has typically no knowledge about the registration order and how to influence it. > This test looks looks good. Does it still work if /* and /*.* are > registered after the others? yes, by looking at the code and some small tests. But the fact, that you are asking the question show, that the precedence order is not fully clear. However, for this case, only a little control is needed.
By these experiments, i would tend to think, that we do not need negative patterns. However, getting more control over the URLspace (e.g. noinherit) would be nice, but that can be as well achieved via the programmatic interface. -g ------------------------------------------------------------------------------ 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
