The query string is ONLY the parameters passed on the URL after the ?,
these can appear on both a GET and a POST (though for POST it would have
to be in the action URL itself, not a form parameter).
If you want the list of parameters from form fields on a POST, you can get
them via
In terms of performance, little difference is caused by splitting
scriptlets (perhaps the extra print noted below.
However, this may be a typo on your part, but
%! String hostname;%
declares an *instance* variable "hostname".
While this assignment:
%
hostname=
I noticed the other day that .tar.gz files I picked up were really just
.tar .. confused the gunzip I was using..
[EMAIL PROTECTED] on 19/01/2001 10:52:33
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:(bcc: Ken X Horn)
Subject: RE: Corrupted files on jakarta server ?
Sorry if I missed it, early on in the thread, but what servlets etc are you
testing the configurations with? In order to assess the performance of the
engine, you should be using simple, easily analysed servlets, doing a
minimum of functionality. Say, a snoop servlet, a session servlet, and
Ask around again ;o) -- the method size limit is actually due to the 16bit
offset inside a class file. It's not javac. JDK 1.3 won't help either
(afaik). I had this problem when using a lot of tags on my page -- they
generate loads of code. You could either using scriptlets to call the
functions
Make sure the DISPLAY variable is not set -- the JVM uses this as an
indication of X. This won't be enough on some VM's, so you can install xvfb
(virtual frame buffer -- a dummy X server). This will make any app think X
is running.
[EMAIL PROTECTED] on 09/01/2001 05:47:22
Please respond
I wouldn't rely on the ready() to get this right - it will depend on
whether data has arrived in the underlying stream (native). This will
probably be system dependent ;o) The only way I've had this working
reliably is to rely on content length headers or chunking. Chunking is
probably best it
Have you tried this on a non-SSL connection?
A general problem with the IO in java (afaik) is that, if you read from the
stream, such that you get a -1 returned, then the stream is effectively
closed. You have to reconnect (I haven't tried SSL on this, but a plain
socket works like this). If
This last one sounds odd but does work sometimes, alternatively, when you
send the add/delete command back, make it a POST on the form, IE will
expect this to be dynamic data and not cache. Make the link submit the form
with appropriate parameters.
Ken.
[EMAIL PROTECTED] on 08/12/2000
