From e0af7556fd39c45c7aa0bf13074bb204230d1ed6 Mon Sep 17 00:00:00 2001 From: remm Date: Fri, 4 May 2007 16:49:06 +0000 Subject: [PATCH] - Changelog update. git-svn-id: https://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk@535325 13f79535-47bb-0310-9956-ffa450edef68 --- webapps/docs/aio.xml | 11 +++++---- webapps/docs/changelog.xml | 59 ++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 66 insertions(+), 4 deletions(-) diff --git a/webapps/docs/aio.xml b/webapps/docs/aio.xml index 4a882bd25..62e0e9bd5 100644 --- a/webapps/docs/aio.xml +++ b/webapps/docs/aio.xml @@ -66,9 +66,10 @@ without blocking. The available and ready methods of the InputStream or Reader may be used to determine if there is a risk of blocking: the servlet should read while data is reported available, and can make one additional read - without blocking. When encountering a read error, the servlet should - report it by propagating the exception properly. Throwing an exception will - cause the error event to be invoked, and the connection will be closed. + should read while data is reported available. When encountering a read error, + the servlet should report it by propagating the exception properly. Throwing + an exception will cause the error event to be invoked, and the connection + will be closed. Alternately, it is also possible to catch any exception, perform clean up on any data structure the servlet may be using, and using the close method of the event. It is not allowed to attempt reading data from the request @@ -82,7 +83,9 @@
  • EventType.END: End may be called to end the processing of the request. Fields that have been initialized in the begin method should be reset. After this event has been processed, the request and response objects, as well as all their dependent - objects will be recycled and used to process other requests.
    • + objects will be recycled and used to process other requests. End will also be + called when data is available and the end of file is reached on the request input + (this usually indicates the client has pipelined a request).
  • EventType.ERROR: Error will be called by the container in the case where an IO exception or a similar unrecoverable error occurs on the connection. Fields that have been initialized in the begin method should be reset. After this event has diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml index 2b2c3fa25..7a0bc22eb 100644 --- a/webapps/docs/changelog.xml +++ b/webapps/docs/changelog.xml @@ -15,12 +15,71 @@
    + + + + More accurate available() method. (remm) + + + Add recycle check in the event object, since it is a facade like the others. (remm) + + + When processing a read event, enforce that the servlet consumes all available bytes. (remm) + + + Add a flag in ContainerBase which could be used in embedded scenarios to avoid a double start + of contexts (this problem generally occurs when adding contexts to a started host). (remm) + + + 42309: Ability to create a connector using a custom protocol specification for embedded. + (fhanik) + + + Add SSL engine flag to AprLifecycleListener. (fhanik) + + + Improve event processing, so that an END event is generated when encountering EOF, and an + ERROR is always generated on client disconnects. (remm) + + + Add declarations for the new XSD files. (remm) + + + + + + + Add heartbeatBackgroundEnabled flag to SimpleTcpCluster. + Enable this flag don't forget to disable the channel heartbeat thread (pero) + + + Possible memory leak when using comet, caused by adding the socket to the poller before + cleaning up the connection tracking structure. (remm) + + + 42308: nextRequest recycles the request, which caused issues with statistics. (remm) + + + Fix non recycled comet flag in the APR connector. (remm) + + + Add heartbeatBackgroundEnabled flag to SimpleTcpCluster. Enable this flag don't forget to disable the channel heartbeat thread (pero) + + Method name cleanup. (fhanik) + + + + + + + Some examples webapp fixes. Submitted by Frank McCown. (remm) +
    -- 2.11.0