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

Re: safe HTTP transport of lock comments

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-02-20 23:59:09 CET

On Fri, 18 Feb 2005, Ben Collins-Sussman wrote:

>
> On Feb 18, 2005, at 9:35 AM, Peter N. Lundblad wrote:
> >>
> >> Yes, but we should still lossily escape them as they go to the client.
> >> People do odd things to their databases sometimes, and don't always go
> >> through our APIs. (Yes, I know that technically that's illegal, and
> >> not our fault, and all that. But there's no reason for Subversion to
> >
> > I see this as database corruption. I think a server error is
> > appropriate
> > in that case.
> >
> >
>
> kfogel and I are persuaded. The final strategy will be:
>
> 1. svn_client_lock() will throw error if it sees a non-xml-safe lock
> comment.
> 2. svn_fs_lock() will do the same.
And svn_fs_attach_lock to be consistent and protect against others using
our APIs in other ways than we do.

rEgards,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Feb 20 23:58:35 2005

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