Jim Jagielski wrote:
On May 14, 2009, at 2:49 AM, jean-frederic clere wrote:
Jim Jagielski wrote:
On May 13, 2009, at 12:01 PM, jean-frederic clere wrote:
Jim Jagielski wrote:
On May 13, 2009, at 10:17 AM, jean-frederic clere wrote:
Jim Jagielski wrote:
OK, I think having 2 more API
Jim Jagielski wrote:
On May 14, 2009, at 10:16 AM, Jim Jagielski wrote:
On May 14, 2009, at 2:33 AM, jean-frederic clere wrote:
Thanks.
The idea of ap_slotmem_mem is to provide an address in the shared
area that can be used for example like the proxy_worker_stat. Using
get/put would
I'm now trying to set up mod_authn_dbb for authentication purpose.
However, I faced to a concern for AuthDBDUserRealmQuery directive.
The example shows the query:
AuthDBDUserRealmQuery \
SELECT password FROM authn WHERE user = %s AND realm = %s
But, I would like to set up the query as
On 14.05.2009 15:49, Joe Orton wrote:
On Thu, May 14, 2009 at 12:51:18PM +0200, Rainer Jung wrote:
On 13.05.2009 22:38, William A. Rowe, Jr. wrote:
Please revert the introduction of a _wrapper struct and let's simply
fix the piped_log structure?
Do we really want to add it to the public API?
Could you please explain why we keep receiving this type of email into
our main enquiries mail box?
Thank you
Mark Pilling
Advice Service Manager
British Lung Foundation
Orleans House
Edmund St
Liverpool L3 9NG
Tel: 08458 505020
Fax: 0151 224 7779
-Original Message-
From: Rainer Jung
On May 14, 2009, at 7:41 PM, Chris Darroch wrote:
Jim Jagielski wrote:
On May 14, 2009, at 3:36 AM, jean-frederic clere wrote:
Yeah... when a do is done, we want to ensure that
none of the slots change since we are touching all slots.
In general, we assume that with get and put, only one
On May 14, 2009, at 7:41 PM, Chris Darroch wrote:
Jim Jagielski wrote:
On May 14, 2009, at 3:36 AM, jean-frederic clere wrote:
Yeah... when a do is done, we want to ensure that
none of the slots change since we are touching all slots.
In general, we assume that with get and put, only one
On May 14, 2009, at 7:14 PM, Chris Darroch wrote:
Jim Jagielski wrote:
Remove mod_slotmem (server/slotmem.c) and the associated
ap_slotmem_*() wrapper functions.
It's just an additional abstraction, agreed. I'm fine with removing
it
but got the impression that people *wanted* that
On May 15, 2009, at 9:02 AM, Jim Jagielski wrote:
On May 14, 2009, at 7:14 PM, Chris Darroch wrote:
Jim Jagielski wrote:
Remove mod_slotmem (server/slotmem.c) and the associated
ap_slotmem_*() wrapper functions.
It's just an additional abstraction, agreed. I'm fine with
removing it
On May 15, 2009, at 10:15 AM, Jim Jagielski wrote:
I'm going to start some of this now...
This is pretty complete now... for some reason, I kept on getting
foo is still in conflict errors when renaming/moving files so
this took more steps that it should have...
On Thu, May 14, 2009 at 04:23:22PM -0700, Chris Darroch wrote:
However, note that any choices we make here also, I believe,
impacts the socache API, which has identical issues around data
consistency in multi-process/multi-thread contexts. Personally
I'd love to see these two APIs be as
Jim Jagielski wrote:
No +1... When do you think you might work on this? I have some cycles
today and would like to start the migration.
Thanks for tackling this ... I see much stuff going on! I fear
the time gap between idea and implementation seems to grow ever larger
these days. I was
KaiGai Kohei wrote:
But, I would like to set up the query as follows:
AuthDBDUserRealmQuery \
SELECT md5(uname || ':' || %s || ':' || upass) FROM uaccount WHERE uname =
%s
^^... to be realmto be user
... ^^
It seems to me we have no
On May 15, 2009, at 2:05 PM, Chris Darroch wrote:
Jim Jagielski wrote:
No +1... When do you think you might work on this? I have some cycles
today and would like to start the migration.
Thanks for tackling this ... I see much stuff going on! I fear
the time gap between idea and
Joe Orton wrote:
w.r.t. locking, my take for socache was: you either duplicate the code
in every provider, or you duplicate the code in every API consumer, so
it wasn't obvious what was best. I expected the latter would be both
simpler and more flexible, so went for that.
It looks like
Chris Darroch wrote:
KaiGai Kohei wrote:
But, I would like to set up the query as follows:
AuthDBDUserRealmQuery \
SELECT md5(uname || ':' || %s || ':' || upass) FROM uaccount
WHERE uname = %s
^^... to be realmto
be user ... ^^
It
Does anyone have anything special that they would like me to
pass on to the ASF board? I could request a budget for our
thousand-open-bugs-bash party.
Roy
On Fri, May 15, 2009 at 6:42 PM, Roy T. Fielding field...@gbiv.com wrote:
Does anyone have anything special that they would like me to
pass on to the ASF board? I could request a budget for our
thousand-open-bugs-bash party.
an httpd party would be cool. it would be nice to crush some of our
KaiGai Kohei wrote:
I think a new directive with formats support is preferable to
keep compatibility with existing directives.
We definitely need compatibility with existing directives.
That's why I figured the extra parameter would be optional --
if you only provided one parameter, the
19 matches
Mail list logo
