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

Re: Hot backup changes

From: <cmpilato_at_collab.net>
Date: 2002-08-22 18:55:25 CEST

=?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:

> cmpilato@collab.net wrote:
> >=?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:
> >
> >
> >
> >>Do we need a post-change-unversioned-item hook?
> >>
> >>
> >
> >Hahaha! I just typing a mail to suggest that, though my scope was
> >smaller: log-message-changed hook.
> >
> Maybe that's better, don't know about what granularity is best. (For
> instance, someday ee may want an acl-changed-hook and lock-changed-hook.)

I'm fine with having a growing list of hooks. For each set of
operations that get dumped into the same hook, we have to package
information that some script has to use to figure out which of those
several operations actually happened. That adds complexity to the
hooks themselves, which heightens the cost of maintainance.

I like to think of hooks as public API calls that are runtime
resolved. I certainly wouldn't try to cram handling for changed ACLs,
locks, and log messages into a single handle_unversioned_thing_mod()

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 18:54:37 2002

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.