Re: Yet more DAV bugs

C. Michael Pilato wrote:
> Justin Erenkrantz wrote:
>> Of course I know that. The catch is that it's not just ne_propfind*
>> that triggers PROPFIND.
>
> Ah. Well, that would certainly put a kink in things.

Actually, can you point out where this happens today? Using st00pid grep
methods, I see that Neon appears to create PROPFIND requests only in one
interface (ne_propfind_create()). That's a public function, but is called
by ne_lock_discover(), ne_simple_propfind(), and ne_propnames(). Those are
all public, but are not called by other Neon functionality.

I can't find any code in libsvn_ra_neon that calls any of these four
interfaces. Did I overlook something?

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand