P: Parse and prepare request S: Service F: Finishing R: Ready K: Keepalive
SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6 - OCEJPAD 6
How To Ask Questions How To Answer Questions
Rob Spoor wrote:If you check just below the table, you'll see this:
P: Parse and prepare request S: Service F: Finishing R: Ready K: Keepalive
You can read what these mean here.
William Brogden wrote:How big are these requests anyway? How are they formatted?
Bill
SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6 - OCEJPAD 6
How To Ask Questions How To Answer Questions
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
2. every POST requests are triggered by server without any consequent request;
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:
2. every POST requests are triggered by server without any consequent request;
That's not right. Whether it's a GET or a POST, if it's HTTP, servers cannot "trigger" unsolicited responses. Some client somewhere had to issue that POST as an HTTP request.
The primary reason why POSTs are offending and not GETs is likely that you are carrying a lot of data in the POST request body. GETs tend to be self-limiting. The larger the request, the longer it's going to take to pipe it in.
There's also a hint that perhaps the application's per-request processing time is a bit long, but that would be have to be measured.
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |