Author: rjung
Date: Tue Jun 27 14:05:40 2006
New Revision: 417587
URL: http://svn.apache.org/viewvc?rev=417587&view=rev
Log:
Clean up todo list.
Modified:
tomcat/connectors/trunk/jk/native/TODO
Modified: tomcat/connectors/trunk/jk/native/TODO
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/native/TODO?rev=417587&r1=417586&r2=417587&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/native/TODO (original)
+++ tomcat/connectors/trunk/jk/native/TODO Tue Jun 27 14:05:40 2006
@@ -114,11 +114,11 @@
not hold true for millisecond time, but in several cases we use the time,
it's not very critical, that it is exact. These cases are related to:
+Some of this is already been done, the remaining parts are:
+
- last_access for usage against timeout value that is ~minutes
- error_time for usage against retry timeout that is ~minutes
-- maintain_time for usage against transfer division interval, that is ~minutes
- uri_worker_map checked for usage against JK_URIMAP_RELOAD=1 minute
-- check against worker_maintain_time which is ~minutes
So I think, it would suffice to set an actual time at the beginning of
the request/response cycle (used by everything before the request is being
@@ -127,8 +127,6 @@
For which cases would it be OK, to use the time before sending to TC:
- uri_worker_map "checked" (uri map lookup starts early)
-- maintain (starts in front of the request)
-- "now" inside retry_worker could be taken from the calling maintain
- setting/testing last_access in
- jk_ajp_common.c:ajp_connect_to_endpoint()
- jk_ajp_common.c:ajp_get_endpoint()
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
