On May 2, 2005, at 2:06 PM, Mark Phippard wrote:
> OK, I can see what this "problem" is. I will let you decide if you
> should
> fix it or not. r14543 now gets the lock owner out of a custom header.
> However, this header was not sent by the server prior to this fix. So
> my
> problem would occur when using an RC2+ client with an RC2 or earlier
> server. Once the server is on RC2+ it will be sending the header that
> the
> client is looking for.
>
> Perhaps the client could fallback to ras->auth_username if it does not
> get
> the header?
>
Nope, this is definitely not a bug. rc2 is not an official release...
and deliberately so, so we can *exactly* make these sorts of
incompatible locking protocol changes. If you're going to use rc's in
production, be sure that clients and servers match.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 2 21:16:57 2005