Re: certain property names cause non-wf XML responses

kfogel@collab.net wrote:
> Agreed.
>
> 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>:

"------- Additional comments from Joe Orton Thu Mar 25 15:04:47 -0700
2004 -------

Julian Reschke brought this up a while back: it's a "don't do that"
issue rather than an escaping issue. The element names being used are
not valid according to the XML Namespaces spec:

  "<svk:signature xmlns="http://..."/>"

and indeed mod_dav has no choice but to reject that request. neon 0.25
and later will also reject responses which include these invalid elements."

Best regards, Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org