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

Re: svn commit: r12241 - trunk/notes/locking

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2004-12-10 19:16:57 CET

On Fri, 10 Dec 2004, Ben Collins-Sussman wrote:

>
> On Dec 9, 2004, at 8:52 PM, Branko ─îibej wrote:
> >>
> > Oy, wait a minute. I thought the expiration date was there only to
> > support generic DAV clients, and that our client should know nothing
> > about it. So why store it in the WC?
> >
>
> The svn_lock_t structure is defined in svn_types.h, available to every
> library on both sides of the network, and is totally transparent.
>
> We agreed that svn clients wouldn't ever have a UI (or API) to *set*
> expiration dates -- that 'svn lock' would always create a non-expiring
> lock. Only mod_dav_svn would allow generic DAV clients to set
> expiration times.
>
> Still, I don't see why would should "hide" the expiration_time field of
> an svn_lock_t from anyone. It's still an important piece of

Since the client will never set an expiration date and the lock
information will only be stored for locks created using the current
working copy, what's the point in storing an expiration time that will
never be there?

Regards,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 10 19:32:36 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.