>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. >You mentioned an objection from Justin related to old clients, is this >it: >http://mail-archives.apache.org/mod_mbox/subversion-dev/200912.mbox/<5c902b9e0912220853j110d893ewe412259e48b7b...@mail.gmail.com> Yes. >Is that about old clients or is it more about things like serf that >use multiple connections? It can even happen to neon connections if the client exceeded the maximum requests allowed per connection. Or some forced closure of the connection due to intermittent network issues on client or server end. With regards Kamesh Jayachandran
