Quoting Jon Stevens <[EMAIL PROTECTED]>: > I'm a member of JSR-053. I will work to change it for the next release > of the spec.
Cool. From what I've heard, the entire TC developer community is behind you 100%. Hell, even Costin agrees with you ... now *that's* truly a red letter day =) > Needless to say, this has a serious impact on Turbine's ability to > function. > It is complete bullshit that it works fine if defined through a servlet, > but not with extension mapping. > > This works: > http://www.foo.com/context/servlet/Turbine/template/Foo.vm > > This doesn't: > http://www.foo.com/context/Foo.vm/bar/ack > > As a result, there is no way for Turbine to work properly with > extension mapping because it relies on passing information in the > PATH_INFO and not QUERY_STRING because of the need for search > engines to be able to archive website information. That sucks, bro. I empathize. I don't know that much about Turbine, to be honest, but would my proposed change to respecting the HTML spec for static content help out with the second case above? I know it's not really static, but if it's outside of the explicit servlet area, would it fall under the auspices of the servlet behavior or the static behavior? Or am I just reaching for a loophole? :) - Christopher /** * Pleurez, pleurez, mes yeux, et fondez vous en eau! * La moitié de ma vie a mis l'autre au tombeau. * ---Corneille */
