On Fri, Aug 20, 2010 at 11:19 AM, Justin Erenkrantz
<justin_at_erenkrantz.com> wrote:
> On Fri, Aug 20, 2010 at 11:15 AM, Lieven Govaerts
> <lieven.govaerts_at_gmail.com> wrote:
>> The memory usage problem is probably still there. Last time I looked
>> at it with valgrind (at the elego days), most of the memory was
>> allocated in the sqlite libraries. This has probably improved a lot
>> with the single-db move, but I haven't tested yet.
>
> FWIW, I didn't see the memory go above ~48MB on my Mac when checking
> out SVN trunk with subversion & serf trunk. So, I'm not tempted to
> pursue it further at this time.
>
> Getting ra_serf in 1.6.x happy with current versions of serf is more
> important (to me). =) -- justin
1.6.x + r879757 backport group now works with serf trunk again. All
'make check' tests (via davautocheck.sh) pass except:
FAIL: merge_tests.py 133: replace that causes a tree-conflict
Considering everything else passes, I'll go out on a limb and say
that's likely not due to the serf version. (I'm guessing it's a known
failure??)
Greg will likely cut a Serf release this weekend that will incorporate
r1401 from serf that will let the old-style authentication handlers in
1.6.x-era ra_serf work. I guess it'll either be 0.7.0 or 0.6.2 - not
sure what his plans are - I just validated against serf trunk. (If we
didn't incorporate r1401 in the new serf release, we'd have to
backport all of the authn changes in ra_serf from trunk and I'd rather
not do that. ra_serf in SVN trunk already uses the new serf authn
framework.)
BTW, those who complain that no one's working on ra_serf hasn't looked
at the diffs between 1.6.x and trunk. New authn framework, digest
auth, Kerberos auth, error handling fixes, better proxy support,
HTTPv2 support, etc. Many many kudos to everyone driving ra_serf
forward! *group hug* -- justin
Received on 2010-08-21 07:24:06 CEST