Ben Collins-Sussman <sussman@collab.net> writes:
> cmpilato@collab.net writes:
>
> > > I don't understand. If 0.20 clients and servers know how to recognize
> > > and handle the new xml attribute, why can't you just finish the
> > > rollout completely in 0.21?
> >
> > If I finish the rollout in 0.21, then 0.21 clients that put binary
> > properties into 0.20 servers will not be able to get them out again.
> > Checkouts will fail, chaos ensues. The solution is the three-step
> > process I detailed, which disallows the addition of XML properties
> > over ra-dav until the server is fully capable of transmitting them.
> > And why don't I turn on the server transmission of binary properties
> > now? Because then a 0.20 server sending bin-props to a 0.19 client
> > will cause the client to store base64'd versions of the properties in
> > the working copy instead of the real prop value.
>
> Ahhhhhhh, all is clear, thanks. I see you need three distinct steps.
>
> But why milestones {.20, .22, .24}, and not {.20, .21, .22}?
Oh, whoops, I accidentally deleted that from my response! And turns
out that that's probably a good thing, because the more I think about
it, {.20, .21, .22} should be just fine. Adjusting milestones
accordingly.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 19 21:50:03 2003