----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Oh boy,
I'll give you a chance to quote me correctly this time. (Maybe try cutting and
pasting... it's safer for you). Come on, Jon. At least *try*
[EMAIL PROTECTED] wrote:
> ----------------------------------------------------------------
> BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
> WHEN YOU POST, include all relevant version numbers, log files,
> and configuration files. Don't make us guess your problem!!!
> ----------------------------------------------------------------
>
> > What do I have to do to get it through to that geek skull of yours, that
> > that is not what I'm looking for. Okay, I just browsed the code
> > (Turbine.java, ParameterParser.java... the works) and the docs. Apart
> > from learning that your client control mechanism leaves a lot to be
> > desired, I did get zip out of it. No surprise there... rm -r Turbine.
> > Subject matter closed.
>
> "client code leaves a lot to be desired"? What exactly does that mean?
>
> > And our code DOES work on any other servlet host other than JServ. URL
> > rewriting or not. Do YOU actually really read messages people send you ?
>
> Yes. And my code works just fine with JServ. So, one would assume that
> your code is the problem. To be nice, I have pointed you at code
> examples that do work so that you can learn how to actually write code
> that actually works. Do you actually read my responses?
>
> > And look at the detour we took. I'm now browsing *freakin* Turbine code,
> > and I was just asking for some feedback on JServ and browser related
> > stuff on encoding parameters in get-forms.
>
> And my response is that it has nothing to do with JServ and that I have
> code that does what you want and works just fine. Also, it has nothing to
> do with browsers, they are just following the specs.
>
> > If you don't know, just say so and shut up. I don't care about Turbine
> > or any of your other ego sensitive issues. I care about finding out why
> > JServ is different with respect to other hosts on this issue. So please,
> > I don't wanna hear from you on any other subject.
>
> Hello? Get it through your head: There is nothing wrong or different with
> JServ with respect to this stuff. The proof is in the code that has been
> presented to you.
>
> I find this totally and absolutely amusing how you are taking all of this
> personally, reading more into my posts than you should and getting all
> worked up about bugs in your own code. I can't stop laughing. ahahhahahaha
> This is so damn funny!
>
> Like I said before...good luck getting your problems solved.
>
> -jon
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html>
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
