I done some works for both TC 3.3 and J-T-C, since the both tree will live for at least some month.
And J-T-C will be used for TC 3.3, 4.0 and also good old TC 3.2.3 ;) I'll commit the change which use TC 3.3 behaviour by default but allow us to fall-back in compatibility mode for old TCs. - Henri Gomez ___[_]____ EMAIL : [EMAIL PROTECTED] (. .) PGP KEY : 697ECEDD ...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 >-----Original Message----- >From: Keith Wannamaker [mailto:[EMAIL PROTECTED]] >Sent: Monday, October 01, 2001 10:52 PM >To: [EMAIL PROTECTED] >Subject: RE: Volunteers for: - RE: TC 3.3: getRequestURI() > > >I thought you were talking about the mod_jk in the TC3.3 >branch. If you're talking j-t-c only, then I don't mind an >Option, as long as it defaults to the 3.3 behavior. > >Keith > >| -----Original Message----- >| From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] >| Sent: Monday, October 01, 2001 11:24 AM >| To: [EMAIL PROTECTED] >| Subject: RE: Volunteers for: - RE: TC 3.3: getRequestURI() >| >| >| >Why can't we implement the 3.3 collaborative solution in 4.0 ? >| >That would maintain compatibility. >| >| And also in TC 3.2.4 ? >| >| >I just hate to provide an option which could result >| >in wrong (double escaped) behavior. At the least, >| >it's one more variable to debug, at worst, it will >| >generate erroneous bug reports. I'd hesitate to >| >add it. >| >| The Option could be hidden and use the TC 3.3 behaviour >| by default... >
