Re: [PATCH] Make svn clients indicate their operation name to backend(right now only to DAV)

"Kamesh Jayachandran" <kamesh_at_collab.net> writes:

>>Let me see if I've got this right. There is a MKACTIVITY that goes to
>>the master, then a PROPFIND that goes to the slave, and finally a
>>CHECKOUT that goes to master. The MKACTIVITY and CHECKOUT go to the
>>master because they are obviously write operations, the PROPFIND goes
>>to the slave because it cannot be distinguished from a read-only
>>operation that doesn't need to access the master. The PROPFIND
>>returns out-of-date info that causes the CHECKOUT to fail.
>
> Yes you got it correct.

So, on the client side libsvn_ra_neon and libsvn_ra_serf could track
whether the PROPFIND needs to go to the master or the slave and then
add a suitable header to the request. libsvn_client doesn't need to
change (which is what I think Justin and Mike are suggesting).

-- 
Philip