On Wed, Feb 3, 2010 at 11:14 AM, Remy Blank <[email protected]> wrote: > Christian Boos wrote: >> I've some ideas regarding the concerns expressed by osimons in the other >> mail about explicit vs. implicit resync and IRepositoryChangeListener, >> but this shouldn't delay the merge. > > Yes, I'm also interested in finding a better / alternative solution. The > hooks are a bit of a pain, and platform-specific on top of that.
The option name `repository_sync_per_request` is bad. In ideal case synchronization should and will be time-based - not request-based, and deprecated option will clutter the getting-bigger list of Trac options. I would rename it to `repository_sync_period`. None means no sync, 0 - every request, any other digital value - minutes between checks. Only one repository should be checked at a time. -- anatoly t. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
