remm 2003/03/18 02:54:54
Modified: coyote/src/java/org/apache/coyote/tomcat5
CoyoteResponse.java
Log:
- Port patch.
- Note: The appCommitted flag is not useful, but I'll leave it in in the event we
want
to separate the application commit (calling flush) with the real socket commit.
I do not quite undestand why the application is allowed to make operations
which have direct impact on the network layer, without allowing the
container to optimize anything.
Revision Changes Path
1.19 +5 -5
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteResponse.java
Index: CoyoteResponse.java
===================================================================
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat5/CoyoteResponse.java,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- CoyoteResponse.java 9 Jan 2003 18:15:05 -0000 1.18
+++ CoyoteResponse.java 18 Mar 2003 10:54:54 -0000 1.19
@@ -364,7 +364,7 @@
* Application commit flag accessor.
*/
public boolean isAppCommitted() {
- return (this.appCommitted || isCommitted());
+ return (this.appCommitted || isCommitted() || isSuspended());
}
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
