On Thu, Feb 3, 2011 at 10:39 AM, Stephan Beal <[email protected]> wrote:

> On Thu, Feb 3, 2011 at 2:38 PM, Stephen De Gabrielle <
> [email protected]> wrote:
>
>> How about a cron job that runs every 10 minutes?
>>  - you could get it to check if there have been any changes, but sync does
>> that anyway. (and doesn't cause much network traffic)
>>
>> I seem to remember a sync function appearing in the ui, but it seems to
>> have gone?
>>
>
> i actually prefer to turn autosync off in most cases (i like to type in
> several commits quickly and push them at once, and i hate the 4-second delay
> between commits while i'm waiting on the autosync), but when i'm editing the
> wiki it "would be comfortable" if the changes were automatically pushed.
> However, i don't feel it is a need-to-have feature, and app slowdown (while
> it waits on the remote, which might not be reachable) and the error
> reporting/handling problems it might introduce make it seem (in hindsight)
> to be a bad idea for a feature.
>

I want to add the ability for Fossil to synchronize itself automatically
with one or more other repositories whenever anything change, said
synchronization driven by a background process.  This would be part of the
same change that allows "hooks" when things change.  Ideally, the auto-sync
would delay for a few seconds (configurable) after each change in case there
are other changes coming right behind the first change - that way a single
sync would capture multiple changes.  Note that since the sync is in the
background, any command-line or web interaction that caused the change would
return immediately and would not be delayed by the background
synchronization process.

I need a good mechanism for kicking off background processes first - a
mechanism that works both for command-line invocations and for CGI and inetd
invocations.  And I'll need functions to test for the existence of existing
background processes so that only one is running at a time.

I've been wanting to do this for a while, but there are other priorities....


>
> --
> ----- stephan beal
> http://wanderinghorse.net/home/stephan/
>
> _______________________________________________
> 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

Reply via email to