[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-18 22:30:03 CEST

Ben Reser <ben@reser.org> writes:
> Yes that's true, which is part of the reason I suggested that we
> discourage their use. I'm adopting Greg Hudson's attitude on issues
> like this. Let's worry about it when we go down that road.
> If we fix it now we know we'll be creating inconvience for people to
> save them from a potential inconvience later, which may never happen.
> I think it's going to be hard to explain to users why we're breaking
> their apps (which we promised we wouldn't) when the reason we are giving
> for doing it is to fix a bug that they're not experiencing any pain
> from.

If we discourage them from using colons, I think they're experiencing
pain (all "svk:" users, for example?).

> If at some point the XML parsers get stricter I imagine the following
> will happen. A small group of people will be early adopters of the new
> library versions. We tell them to revert to a previous version for the
> time being. We take the painful option of breaking compatability at the
> next minor release, which we'll probably move up to release ASAP to deal
> with this.
> My biggest priority is trying to keep this bug out of peoples faces. At
> this point it's a correctness issue. If and when my workaround fails to
> hold I'll support any compatability breaks needed to fix the problem.

That may be a good strategy, must mull it over. In the meantime, the
meat of my proposal is the decoding scheme, which we want to get in
ASAP anyway, so I'll continue working.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 19 00:20:33 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.