on 7/25/02 4:04 PM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote:
> Jon, people don't have time to chase down vendors to fix things and even > if they started the process it could take forever. If you are not > prepared to personally help in the process of getting iPlanet to fix > their implementation then the change should stay, again provide it works > for everyone. About 3-4 months ago, when this issue first cropped up, I sent a message to the JSR-154 (Servlet API) list detailing the problem. > It's just plain silly to screw people not using an OSS > servlet containers where they don't have access to fix things easily. > Some people don't have a choice over what container they use and > obviously don't have the time to go tracking down developers for > iPlanet. Think of it this way...people choose commercial containers/software because they expect that they can get support from it and be able to call someone up who will fix problems when they come up. This is a perfect example of how broken that thinking is. So, if Turbine is doing the right thing and the servlet engine isn't, should we expect Turbine to always work around it? I don't think so. Let these people who choose to use the broken containers (especially the commercial ones) call up their support and get them to fix it. I'm still -1 on this. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
