Brian Akins wrote:
Jean-frederic Clere wrote:
Do you mean the proxy back-end connections?
I am thinking of a more general purpose slotmem not particularly
tied to proxy. Maybe have some wrapper functions that create a
slotmem based on threads x procs and can be access using
Jean-frederic Clere wrote:
Do you mean the proxy back-end connections?
I am thinking of a more general purpose slotmem not particularly tied
to proxy. Maybe have some wrapper functions that create a slotmem
based on threads x procs and can be access using r-connection.
(internally slotmem
Brian Akins wrote:
Jean-frederic Clere wrote:
Do you mean the proxy back-end connections?
I am thinking of a more general purpose slotmem not particularly tied
to proxy.
++1. Making it proxy specific really doesn't allow for the
kind of abstraction and usage that would make it
Brian Akins wrote:
Jean-frederic Clere wrote:
Do you mean the proxy back-end connections?
I am thinking of a more general purpose slotmem not particularly
tied to proxy. Maybe have some wrapper functions that create a
slotmem based on threads x procs and can be access using
Some comments inline.
Regards
Rüdiger
On 19.07.2006 14:18, [EMAIL PROTECTED] wrote:
Author: jfclere
Date: Wed Jul 19 05:18:10 2006
New Revision: 423444
--- httpd/httpd/branches/httpd-proxy-scoreboard/modules/mem/mod_plainmem.c
(added)
+++
Ruediger Pluem wrote:
+static apr_status_t ap_slotmem_create(ap_slotmem_t **new, const char
*name, apr_size_t item_size, int item_num, apr_pool_t *pool)
In my thought of a slotmem or scoreboard item_num is max threads *
max procs just like the normal scoreboard. Or has this morphed into
Ruediger Pluem wrote:
Some comments inline.
Regards
Many thanks
Cheers
Jean-Frederic
Rüdiger
On 19.07.2006 14:18, [EMAIL PROTECTED] wrote:
Author: jfclere
Date: Wed Jul 19 05:18:10 2006
New Revision: 423444
---
