Received: (qmail 80895 invoked by uid 501); 24 Jan 2001 18:31:23 -0000
Message-Id: <20010124183123.80894.qmail@apache.org>
Date: 24 Jan 2001 18:31:23 -0000
From: Mark Libucha <MarkLibu@cs.com>
Reply-To: MarkLibu@cs.com
To: submit@bugz.apache.org
Subject: More flexible timeout API
X-Send-Pr-Version: 3.110

>Number:         7123
>Category:       apache-api
>Synopsis:       More flexible timeout API
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Wed Jan 24 10:40:04 PST 2001
>Closed-Date:    Wed Jan 24 16:35:44 PST 2001
>Last-Modified:  Wed Jan 24 16:35:44 PST 2001
>Originator:     MarkLibu@cs.com
>Release:        1.3.12
>Organization:
>Environment:
Any/all
>Description:
In order to get around having to use the Apache global timeout value for all timeouts, we would like to see the following calls (name them what you will) added to the next release of Apache. We don't believe these additions would in any way affect the current functionality of any part of the web server. It would need to be documented that ap_reset_timeout, if called, would still use the global timeout in all cases.

API_EXPORT(void) ap_flexible_hard_timeout(char *name, request_rec *r, int seconds)
{
    timeout_req = r;
    timeout_name = name;

    ap_set_callback_and_alarm(timeout, seconds);

}

API_EXPORT(void) ap_flexible_soft_timeout(char *name, request_rec *r, int seconds)
{
    timeout_name = name;

    ap_set_callback_and_alarm(timeout, seconds);

}

Thanks! (Obviously, the request_rec* argument is not needed in the second call, but we left it there for uniformity.)
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: fanf
State-Changed-When: Wed Jan 24 16:35:44 PST 2001
State-Changed-Why:
Sorry, we aren't making that kind of change to 1.3 any more,
and 2.0 doesn't use timeouts in the same way.
Thanks for using Apache!
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]