On Sat, Sep 10, 2011 at 10:32 AM, Remigiusz Modrzejewski <[email protected] > wrote:
> Hi, > > I'd like to know where we are in the topic of hooks. Their lack is one of > the major setbacks of using Fossil. The last time I've noticed a discussion > on their topic it was said, that it's blocked by inability to start > background processes on Windows. Now there is a way to run Fossil itself in > background on Windows. Has this helped towards getting hooks into main line? > The current limiting factor is DRH bandwidth. I have way too much else going on and this is a low priority issue for me. But you can help by contributing code! 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. As part of the hook mechanism, I think we also need auto-sync between server instances. For example, Fossil itself is stored on three separate servers: http://www.fossil-scm.org/ in Dallas, http://www2.fossil-scm.org/ in New York, and http://www3.fossil-scm.org/ in Fremont. I currently keep these all in sync by setting a cron job to run "sync" every couple of hours. But it would be much better if one could enter, on each server, the names of other servers with which it should automatically synchronize whenever new information arrives. This auto-sync should be smart about avoiding sync-loops. Hence if server A gets new content and then auto-syncs to server B, server B should know that it got its new information from A and should avoid auto-syncing back to server A. Some other projects (besides hooks) that I think would be good to work on, for anybody who is interested: (1) Making Fossil more RESTful, and adding JSON replies. Stephan Beal is already working on this, but I'm sure he'd like to have collaborators. (2) Add the ability to push/pull/sync just a specific branch, as an alternative to the current behavior of push/pull/sync of everything. The current behavior should continue as the default. Single-branch push/pull/sync should be a command-line option. (3) Use the FTS4 full-text search engine of SQLite to implement full-text search over the entire repository history. > > > Kind regards, > Remigiusz Modrzejewski > > > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
