On Sat, Sep 10, 2011 at 1:53 PM, Richard Hipp <[email protected]> wrote: > The hook mechanism should include a delay. This is because client-to-server > push operations can occur in multiple stateless steps, and we really want to > wait and run the hooks after all steps of the push operation are complete. > So, for example, after the first push step, the server says to itself "I'm > going to run the hooks if I don't get any new information within 15 > seconds." Then as additional rounds of push arrive, the counter is reset. > The 15-second wait interval should be configurable.
I assume that similar logic would apply for running pre-hooks - ie, the pre hook is run only for the initial step of an operation. > As part of the hook mechanism, I think we also need auto-sync between server > instances. I have actually been looking into this, though not yet written any code. But now, I think I can put more time into this. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
