Following up to try and direct a solution...
On Wed, Apr 20, 2011 at 03:15, Arwin Arni wrote:
> Hi,
>
> From what I've read in the responses, I understand that the dav_cache is not
> a NON-NULL field... and that neon uses it and serf doesn't.
>
> I've also not gone deep enough into the code to un
Hi,
From what I've read in the responses, I understand that the dav_cache
is not a NON-NULL field... and that neon uses it and serf doesn't.
I've also not gone deep enough into the code to understand what
information is actually getting stored there, but I do believe this
holds some informat
On Apr 19, 2011 12:10 PM, "Hyrum K Wright" wrote:
>...
>
> False. This is a *cache*, meaning, if it is NULL you don't lose any
> information, it may just take longer to get that information. If the
> cache is NULL, neon will populate it as needed for increased
> performance.
>
> Note that the ca
I believe that when ra_serf touches a node, the dav_cache will be set to
null. wc_db basically enforces that.
On Apr 19, 2011 12:11 PM, "C. Michael Pilato" wrote:
> ra_serf in trunk, speaking HTTPv2 with the server, doesn't make use of the
> dav_cache. But I can see how that might be a problem whe
ra_serf uses HTTPv2 which does not use the dav_cache. ra_neon has not been
upgraded to use the new protocol.
When ra_serf talks HTTPv1, it *may* use dav_cache, but we may have just left
that out and taken the speed hit (I don't recall)
Cheers,
-g
On Apr 19, 2011 11:58 AM, "Arwin Arni" wrote:
> H
ra_serf in trunk, speaking HTTPv2 with the server, doesn't make use of the
dav_cache. But I can see how that might be a problem when switching between
serf and neon, because neon *does* consult the dav cache (which in your
case, I'm guessing, must be stale).
At a minimum, if ra_serf isn't going t
On Tue, Apr 19, 2011 at 10:57 AM, Arwin Arni wrote:
> Hi All,
>
> NODES.dav_cache in wc.db is always set to NULL in serf.
>
> Is it intentional?
Yes. Serf does not require this cache.
> If not attached patch would fix it.
>
> Why I am concerned?
>
> I was testing one scenario(master-slave setup
7 matches
Mail list logo
