https://bz.apache.org/bugzilla/show_bug.cgi?id=66541
--- Comment #7 from Mark Thomas <ma...@apache.org> --- (In reply to Tom Whitmore from comment #6) > Thanks. The "wrapped one" is the outer one; I use wrapped & underlying as a > frequent terminology, it works well & is clear semantically. On that we are going to have to agree to disagree. The cache URL handler has references to both the original resource URL and that cache URL. I can see how either of those could be viewed as wrapped. That you and I seem to view this differently - and both us of seem fairly sure we are right - tells me any variation on the theme of "wrap" is not the right one. Replacing "associatedURL" with "cacheURL" is an alternative possibility. The first step is to fix the bug - which I'll do shortly. The second step is to take another look at the logic. I'm not sure the "... == u1" tests are required at all. I think those methods are only going to be called from the URL instance that was created with the handler instance so they are always going to be true. If that is the case, I'll simplify (remove) the logic. Finally there is the rename to make things clearer. Current front-runner is cacheURL, with the caveat a reason not to use it / a better idea may occur to me while working on this issue. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
