On Sun, Aug 19, 2001 at 08:29:58PM +0200, Harald Radi wrote:
>...
> >> Another possibility is to fork the commit-email and run it in the
> >> background, letting the final commit request complete quickly (since we
> >> generate it based on a specific revision, this is easy and robust (unlike
> >> the race conditions we see in CVS re: generating the commit email)).
>
> > Err.. Why didn't you do this in the first place? I'd think you'd only
> > want synchronous hooks pre-commit, as opposed to post-commit where
> > synchronous events don't make sense? (i.e. hogging up the Apache thread
> > waiting for it to finish)
>
> synchronous post-commit hooks do make sense! consider the case that you
> have to check out the
> repository on every commit (e.g. a svn managed webroot) the commit
> should finish _after_ the
> checkout and the post-commit script should be able to issue warnings /
> errors.
We can do synchronous and async hooks. The servers runs the hook scripts
synchronously. Those scripts can then place things into the background (and
detach them) if they do not require them to be synchronous.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:36 2006