On 10/21/2008 01:09 AM, Nick Kew wrote:
[EMAIL PROTECTED] wrote:
--- httpd/httpd/trunk/modules/http/http_request.c (original)
+++ httpd/httpd/trunk/modules/http/http_request.c Sat Sep 20 04:58:08
2008
@@ -257,24 +297,7 @@
ap_die(access_status, r);
}
-/* Send an
[EMAIL PROTECTED] wrote:
--- httpd/httpd/trunk/modules/http/http_request.c (original)
+++ httpd/httpd/trunk/modules/http/http_request.c Sat Sep 20 04:58:08 2008
@@ -257,24 +297,7 @@
ap_die(access_status, r);
}
-/* Send an EOR bucket through the output filter chain. When
On 9/21/08 2:17 AM, Bing Swen [EMAIL PROTECTED] wrote:
But an optimal
network i/o model needs a layer that maps a *request* to a thread, so that a
worker thread (or process) will not have to be tied up entirely with a
single connection during the whole life time of the connection. Instead, a
Akins, Brian wrote:
On 9/21/08 2:17 AM, Bing Swen [EMAIL PROTECTED] wrote:
But an optimal
network i/o model needs a layer that maps a *request* to a thread, so that a
worker thread (or process) will not have to be tied up entirely with a
single connection during the whole life time of
Akins, Brian wrote:
I'm all for making httpd faster, scale better, etc. I just don't want to be
extremely disappointed if we rewrite it all and gain nothing but a more
complicated model. If we get great gains, wonderful, but I'd like to see
some actually numbers before we all decided to
Akins, Brian wrote:
On 9/21/08 2:17 AM, Bing Swen [EMAIL PROTECTED] wrote:
But an optimal
network i/o model needs a layer that maps a *request* to a thread, so that a
worker thread (or process) will not have to be tied up entirely with a
single connection during the whole life time of the
On Sep 22, 2008, at 11:51 AM, Paul Querna wrote:
No, in pure requests/second, there will not be a significant
difference.
Today, a properly tuned apache httpd, with enough RAM, can keep up
with the 'fastest' web servers of the day, like lighttpd. Most of
the benchmarks where we do
Paul Querna [EMAIL PROTECTED] wrote on 2008-9-21 4:21
Graham Leggett wrote:
I know there are likely huge problems with this, but I would like to see
how far
we can push the Event MPM, figure out what to do better, if there is
anything, and then really dive into the 3.0 development before
On Sep 20, 2008, at 4:31 PM, Paul Querna wrote:
Jim Jagielski wrote:
On Sat, Sep 20, 2008 at 11:58:09AM -, [EMAIL PROTECTED] wrote:
-#define ap_queue_empty(queue) ((queue)-nelts == 0)
+#define ap_queue_empty(queue) ((queue)-nelts == 0
APR_RING_EMPTY(queue-timers ,timer_event_t, link))
On Sat, Sep 20, 2008 at 11:58:09AM -, [EMAIL PROTECTED] wrote:
Does anyone besides Rdiger read commit emails :-) ?
No :)
+else {
+/* X: lol, pool allocation without a context from any
thread.Yeah. Right. MPMs Suck. */
+te = malloc(sizeof(timer_event_t));
[EMAIL PROTECTED] wrote:
Using this basic framework, you can return SUSPENDED from an HTTP Handler,
and then register a callback that is invoked by the MPM at a later time.
This initial version only supports _timers_ as callbacks, but in the future I
would like to add things like wait for
Graham Leggett wrote:
I know there are likely huge problems with this, but I would like to
see how far
we can push the Event MPM, figure out what to do better, if there is
anything, and then really dive into the 3.0 development before ApacheCon.
How difficult would this be to support in the
Nick Kew wrote:
On 20 Sep 2008, at 12:58, [EMAIL PROTECTED] wrote:
Introduce Suspendable Requests to the Event MPM.
Hmmm ...
Are you sure this belongs in the MPM?
The core problem is, where do we have an Event scheduling and worker
thread system. The best place to keep that is the MPM
On 09/20/2008 01:58 PM, [EMAIL PROTECTED] wrote:
Author: pquerna
Date: Sat Sep 20 04:58:08 2008
New Revision: 697357
URL: http://svn.apache.org/viewvc?rev=697357view=rev
Log:
Introduce Suspendable Requests to the Event MPM.
Modified: httpd/httpd/trunk/include/ap_mpm.h
URL:
Ruediger Pluem wrote:
+
+typedef void (ap_mpm_callback_fn_t)(void *baton);
+
+/* XXX: only added support in the Event MPM */
+AP_DECLARE(void) ap_mpm_register_timed_callback(apr_time_t t,
+ap_mpm_callback_fn_t
*cbfn,
+
15 matches
Mail list logo
