[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: certain property names cause non-wf XML responses

From: <kfogel_at_collab.net>
Date: 2004-10-20 16:12:25 CEST

Julian Reschke <julian.reschke@gmx.de> writes:
> > I think your custom-report solution also lessens the urgency of
> > #1971,
> > because there aren't any important compatibility stages. We can add
> > the feature to client and server simultaneously, and each would retain
> > the ability to work the old way when faced with an older interlocutor.
> > The only thing with compatibility implications is for the server to
> > stop sending DAV-incompatible props over DAV. But as there's no
> > corresponding client change to that, it's simply a one-time thing that
> > we do at 2.0 (but not before, of course, because it would break 1.x
> > client compatibility).
> > Sanity check: does the above make sense?
> Yes. But keep in mind that changes in the neon lib may be upcoming
> which would force you to do that change earlier; quoting Joe from
> <http://subversion.tigris.org/issues/show_bug.cgi?id=1807>:

Sure, we can make that decision if/when it becomes necessary.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 20 18:03:34 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.