I didn't mean to start a debate when I complained about Webware's simplistic URI mapping strategy. I was just giving a heads up to anyone trying to go where I had been. It looks like Kendall had already figured it out.
Geoff: I don't have a problem with the current behavior being the default. When I designed URLDecode, preserving the existing behavior was a major goal. I don't remember why URLDecode never made it into Webware -- probably only because I didn't have the energy/time to polish it and push it through, or maybe because I just got distracted doing other things. (The perfectionist in me wanted to fix too many things. Starting Jaguar with a clean slate seemed easier.) Anyway, Geoff is at worst ambivalent, and there are at least three people who want very much to have the URI decoding fixed. What do we need to do to get it there? I have created two wiki topics for the discussion, since I think this fits better in wikispace than in mailing list space. http://webware.colorstudy.net/twiki/bin/view/Webware/ManagingTheURISpace is for high-level best practices that we have discussed in the WebDAV thread. http://webware.colorstudy.net/twiki/bin/view/Webware/UriMapping is for a concrete implementation that can go into Webware RSN that can replace the current filesystem-centric mapping strategy. _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
